Re: pg_dump and public schema

On 3/5/20 6:57 AM, Олег Самойлов wrote: Thanks. I expected that the database restored from its dump must be exactly the same. As it was before. But something in PostgresQL changes and not always for the good. From what I see: 1) pg_dump -C -U postgres -d sch_test CREATE DATABASE sch_test W

Re: pg_dump and public schema

Thanks. I expected that the database restored from its dump must be exactly the same. As it was before. But something in PostgresQL changes and not always for the good. > 4 марта 2020 г., в 19:19, Adrian Klaver > написал(а): > > I believe this is the latest information on public schema handli

Re: pg_dump and public schema

On 3/4/20 5:42 AM, Олег Самойлов wrote: Hi all. PostgresQL 12.1. Strange behaviour with pg_dump and absent public schema. I droped public schema and I work under "username" schema. => \dn List of schemas Name | Owner ---+--- olleg | olleg (1 row) Dump now pg_dump -U postgres -C

Re: pg_dump and public schema

Hi, I think "create database" always creates the "public" schema. So, all is well. All you have to do is drop it after running the dump.sql script. Cheers, Paul On Wed, Mar 4, 2020 at 2:43 PM Олег Самойлов wrote: > > Hi all. PostgresQL 12.1. Strange behaviour with pg_dump and absent public > s

pg_dump and public schema

Hi all. PostgresQL 12.1. Strange behaviour with pg_dump and absent public schema. I droped public schema and I work under "username" schema. => \dn List of schemas Name | Owner ---+--- olleg | olleg (1 row) Dump now pg_dump -U postgres -C olleg >dump.sql -- -- PostgreSQL database d