From: | "ceccareb(at)talusmusic(dot)com" <ceccareb(at)talusmusic(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15263: pg_dump / psql failure. When loading, psql does not see function-based constraints or indices |
Date: | 2018-07-07 14:50:46 |
Message-ID: | CB84C791-BAA6-4BAC-AF94-BFF2D67FCD8B@talusmusic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Seems like a reasonable diagnosis. Apparently someone introduced this problem into 10.x. 9 works fine.
Is there anything I can do? Or do know if someone is trying to fix this one?
Thanks!
Brian Ceccarelli
919-815-0126
> On Jul 7, 2018, at 3:14 AM, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
>> On 06.07.18 18:19, PG Bug reporting form wrote:
>> I have a database with a table with a function-based check constraint.
>> The database has another table with a function-based index.
>> I dump with COPY statements (the default).
>>
>> When I load the database from the dump I just created, loading (via psql)
>> logs error messages. Postgres cannot find functions inside the function the
>> constraint or index invokes.
>
> I think this and your subsequent report are all instances of the problem
> that pg_dump cannot see into the function body to check what database
> objects it depends on, so it cannot produce a working ordering of the
> objects.
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-07-07 23:07:43 | BUG #15266: libpq: PQgetvalue fails with Break at address "0x8000fb50" Signal : SIGSEGV:Segmentation fault) |
Previous Message | Tom Lane | 2018-07-07 14:48:06 | Re: BUG #15263: pg_dump / psql failure. When loading, psql does not see function-based constraints or indices |