Postgres Pro
Downloads
Home   >   mailing lists

Re: fix for pg_dump (caused by array output syntax changes) - Mailing list pgsql-patches

From Tom Lane
Subject Re: fix for pg_dump (caused by array output syntax changes)
Date
Msg-id 14932.1094489303@sss.pgh.pa.us
Whole thread Raw
In response to fix for pg_dump (caused by array output syntax changes)  (Weiping <laser@qmail.zhengmai.net.cn>)
Responses Re: fix for pg_dump (caused by array output syntax changes)
List pgsql-patches
Tree view 
Weiping <laser@qmail.zhengmai.net.cn> writes:
> don't know if it's too simple, and didn't solved for quite a period of time.
> But I still need pg_dump to do my backup, so do a simple(but ugly) hack.

This isn't going to be applied because pg_dump is not broken ... at
least not against CVS tip.  You apparently are running a pre-beta
backend that numbered ACL entries from zero.

            regards, tom lane

pgsql-patches by date:

Previous
From: Weiping
Date:
Subject: fix for pg_dump (caused by array output syntax changes)
Next
From: Tom Lane
Date:
Subject: Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1