Re: pg_get_triggerdef in pg_dump

Поиск
Список
Период
Сортировка
От Christopher Kings-Lynne
Тема Re: pg_get_triggerdef in pg_dump
Дата
Msg-id 125c01c33484$070c4d40$6500a8c0@fhp.internal
обсуждение исходный текст
Ответ на pg_get_triggerdef in pg_dump  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Ответы Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
Список pgsql-hackers
> Seems like a good idea to me --- we've been trying to reduce pg_dump's
> knowledge of backend nitty-gritty, and this would be another small step
> in the right direction.
>
> > Also, it doesn't format them as nicely as the current pg_dump code...
>
> That's fixable no?  I guess you might want to consider what psql's \d
> display will look like too, but I don't recall that we ever promised
> anyone that the pg_get_xxx functions would output no unnecessary
> whitespace.

We make pg_get_xxx2 functions that return a formatted version.  Internally,
we just add an extra boolean parameter to the pg_get_triggerdef() function
in ruleutils and we call that true or false depending...

Chris



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pg_get_triggerdef in pg_dump
Следующее
От: Dennis Björklund
Дата:
Сообщение: Re: confused with encodings