Re: pg_restore depending on user functions

From: Дмитрий Иванов <firstdismay(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: pg_restore depending on user functions
Date: 2021-11-17 01:33:40
Message-ID: CAPL5KHpnvkoch1ViCKWmPoNcSQM3j671ohGwtwRWOrOWwGMVPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

Ok, I'll do it.
Am I correct in understanding that I need to dump --schema-only in SQL
format and then delete everything, leaving one chain for example? If so, it
will have to be postponed until the weekend.

ср, 17 нояб. 2021 г. в 01:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay(at)gmail(dot)com>
> writes:
> > --Line 4048:
> > CREATE TABLE bpd.class (
>
> There are still a lot of problems in this example:
>
> * references to nonexistent columns val_text, val_bytea, val_json
>
> * int_class_ext refers to int_class_ready, int_class_path,
> bpd.object, which weren't supplied
>
> I figured maybe I didn't need int_class_ext, since it doesn't appear
> to be referenced elsewhere. But with the objects I have, pg_dump
> doesn't do anything wrong; the output can be loaded just fine.
>
> Please, send a self-contained SQL script that you have actually
> tested to be loadable, and which produces a database that
> causes pg_dump to do the wrong thing.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-11-17 01:47:44 Re: pg_restore depending on user functions
Previous Message Masahiko Sawada 2021-11-17 01:06:15 Re: References to parameters by name are lost in INSERT INTO ... SELECT <parameter value> .... statements in case of routines with the SQL-standard function body

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2021-11-17 01:47:44 Re: pg_restore depending on user functions
Previous Message Tomas Vondra 2021-11-16 22:03:35 Re: Plans with bad estimates/paths