Re: fix for pg_dump (caused by array output syntax changes)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Weiping <laser(at)qmail(dot)zhengmai(dot)net(dot)cn>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: fix for pg_dump (caused by array output syntax changes)
Date: 2004-09-06 16:48:23
Message-ID: 14932.1094489303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Weiping <laser(at)qmail(dot)zhengmai(dot)net(dot)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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-09-06 23:57:42 Re: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1
Previous Message Weiping 2004-09-06 16:02:53 fix for pg_dump (caused by array output syntax changes)