citusdata / citusdata/citus

`citus_prepare_pg_upgrade` assumes `public` schema exists

Open
#5,447 1 comment 0 reactions 0 assignees View on GitHub
bug dev_reported
Dominant language
C
Stars
12.8k
Forks
794
Avg merge
2d 14h
Merged PRs (30d)
31

Description

Maybe we should create `public` schema ourselves ?, or is this the intended behavior ?:

```sql
create schema my_schema;
set search_path to my_schema;
drop schema public cascade;
create extension citus;
select citus_prepare_pg_upgrade();
NOTICE: aggregate array_cat_agg(anycompatiblearray) does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
NOTICE: schema "public" does not exist, skipping
ERROR: schema "public" does not exist
CONTEXT: SQL statement "CREATE TABLE public.pg_dist_partition AS SELECT * FROM pg_catalog.pg_dist_partition"
PL/pgSQL function citus_prepare_pg_upgrade() line 32 at SQL statement
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.