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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: fix for pg_dump (caused by array output syntax changes)
Дата
Msg-id 14932.1094489303@sss.pgh.pa.us
обсуждение исходный текст
Ответ на fix for pg_dump (caused by array output syntax changes)  (Weiping <laser@qmail.zhengmai.net.cn>)
Ответы Re: fix for pg_dump (caused by array output syntax changes)
Список pgsql-patches
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Weiping
Дата:
Сообщение: fix for pg_dump (caused by array output syntax changes)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1