On 10/3/23 02:59, Harry Green wrote:
Dear All,
I'd like to thank you for your excellent input on this problem. We have
now resolved this issue and I thought I would mention how. The topic of
the function being used as a check constraint had come up and I had
rejected this because it was the
Dear All,I'd like to thank you for your excellent input on this problem. We
have now resolved this issue and I thought I would mention how. The topic of
the function being used as a check constraint had come up and I had rejected
this because it was the name given to a function which does
On Wed, Sep 20, 2023 at 2:06 PM Harry Green wrote:
> I attach the text of the entire create function instruction, and also of
> the create table instruction.
>
>
The restore is not going to execute functions on its own and you've only
shown two create statements. Somewhere else in your dump
Thanks for your answer,I have done a complete pg_dump and complete restore,
and tried all forms of complete pg_dumps and restores (i.e. the different
formats). There is no partial or tables only or data only dumping or restoring.
Further, you refer to a 'check constraint' but this is just a
On 9/18/23 14:46, Johnson, Bruce E - (bjohnson) wrote:
Reply to list also.
Ccing list to return your answer there.
It turned out that for some reason the perl DBD::Pg module was trying to
connect twice, the first failed because of a typo in the password, the
second because it tried to connect
