fix for pg_dump (caused by array output syntax changes)
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.
Wish it helps.
regards laser
Attachments:
pg_dump.patchtext/plain; name=pg_dump.patchDownload+4-4
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
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.
Got it: The code are up-to-date, but I didn't initdb,
so the system catalog didn't update thus the pg_dump broken.
thanks and regards laser