error "graphql_public" does not exists with cli supabase start

[GaryAustin1]

Bug report

A customer using the CLI with a new install is getting this:

"I'm trying to execute. supabase start but i got this error Error: Error starting database: ERROR: schema "graphql_public" does not exist"

No info yet, but putting this out here in case the code added here for pg_graphql is already being installed by the CLI and there might be an issue with the pg_graphql extension. Would not have expected customer to run into it yet.

@olirice I noticed the push 4 days ago, so flagging in case an early issue has been found.

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

Additional context

Add any other context about the problem here.

[olirice]

thanks @GaryAustin1 and sorry for the slow reply

We rolled out pg_graphql in the base image and things were briefly out of sync with the CLI. Could you please try the commands again and let me know if you're still seeing the issue?

[GaryAustin1]

@olirice I was reporting it as a user on discord hit it and I knew you were in the process of rolling it out but not announced yet... Figured something got "released" early.
I pointed them here, but they did not comment. I'll see if I can find the post again, but I'm sure by now they got past it.

[simlevesque]

@GaryAustin1 I'm actually having this same issue. I can't start supabase after linking with the remote db. On 23.10.

[olirice]

@soedirgo ^

do you have any ideas how that could happen 23.10?

[soedirgo]

Probably not specific to 23.10, rather the same problem you mentioned re: supabase/postgres image being out of sync. Should be fixed with #232, coming out in the next release.

[simlevesque]

I actually had this bug before 23.10 so that makes sense. I should have said that previously.

[simlevesque]

@olirice I'm afraid that the problem is still present.

~/w/supabase-test  main• ❱ supabase start
Error: supabase start is already running. Try running supabase stop first.
~/w/supabase-test  main• [1] supabase stop
Stopped local development setup.
~/w/supabase-test main• ❱ supabase start
⣻ Applying migration 20220401210615_remote_commit.sq
Error: Error starting database: ERROR:  schema "graphql_public" does not exist

⏎                                                                                                                                                                                                               ~/w/supabase-test  main• 46.1s [1] supabase -v
0.24.0

I even tried to reset all my local files, I still get the same issue. It pulled the new supabase/postgresql.

Here's the content of 20220401210615_remote_commit.sql

-- This script was generated by the Schema Diff utility in pgAdmin 4
-- For the circular dependencies, the order in which Schema Diff writes the objects is not very sophisticated
-- and may require manual changes to the script to ensure changes are applied in the correct order.
-- Please report an issue for any failure with the reproduction steps.

CREATE OR REPLACE FUNCTION graphql_public.graphql(
	"operationName" text DEFAULT NULL::text,
	query text DEFAULT NULL::text,
	variables jsonb DEFAULT NULL::jsonb,
	extensions jsonb DEFAULT NULL::jsonb)
    RETURNS jsonb
    LANGUAGE 'plpgsql'
    COST 100
    VOLATILE PARALLEL UNSAFE
AS $BODY$
    DECLARE
        server_version float;
    BEGIN
        server_version = (SELECT (SPLIT_PART((select version()), ' ', 2))::float);

        IF server_version >= 14 THEN
            RETURN jsonb_build_object(
                'data', null::jsonb,
                'errors', array['pg_graphql extension is not enabled.']
            );
        ELSE
   	        RETURN jsonb_build_object(
                'data', null::jsonb,
                'errors', array['pg_graphql is only available on projects running Postgres 14 onwards.']
            );
        END IF;
    END;
$BODY$;

ALTER FUNCTION graphql_public.graphql(text, text, jsonb, jsonb)
    OWNER TO supabase_admin;

If you need my DB id or anything just ask me.

[olirice]

@simlevesque yes, please send your project ref and I'll take a look

[soedirgo]

I tried replicating this and don't get the graphql_public.graphql DDL above in remote_commit.sql.

One thing you can try to fix this is to empty (not remove) remote_commit.sql and put CREATE EXTENSION IF NOT EXISTS pg_graphql SCHEMA extensions; in (undocumented) supabase/extension.sql. We're working on fixing Postgres permissions so that you can do CREATE EXTENSION in a migration, which you currently can, but wouldn't work when you push the migration.

[princemaple]

Same issue.

If I comment out the 2 graphql_public clauses, I still get this:
function extensions.moddatetime() does not exist

An issue with all the extensions?

My project was created mostly in the browser. I only just started using the cli now and did remote commit the first time.

[soedirgo]

Yes, an issue with all extensions unfortunately. In your case you might want to do CREATE EXTENSION IF NOT EXISTS moddatetime SCHEMA extensions; as well.

[princemaple]

Thanks for the confirmation and the workaround. It's a pretty amazing product nonetheless.

[simlevesque]

@olirice

jwycethvnuypxtlvclfs

Sorry for the late reply.