| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_restore depending on user functions |
| Date: | 2021-11-16 20:04:06 |
| Message-ID: | 2254203.1637093046@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
=?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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-11-16 21:52:57 | 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 |
| Previous Message | Дмитрий Иванов | 2021-11-16 16:57:38 | Re: pg_restore depending on user functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Wildish | 2021-11-16 20:22:44 | Plans with bad estimates/paths |
| Previous Message | DAVID ROTH | 2021-11-16 19:51:36 | Re: Postgres Equivalent of Oracle Package |