Re: truncating pg_multixact/members

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: truncating pg_multixact/members
Дата
Msg-id 31820.1392230043@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: truncating pg_multixact/members  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: truncating pg_multixact/members  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> In this new version, I added a couple of fields to VacuumStmt node.  How
> strongly do we feel this would cause an ABI break?  Would we be more
> comfortable if I put them at the end of the struct for 9.3 instead?

In the past we've usually added such members at the end of the struct
in back branches (but put them in the logical place in HEAD).  I'd
recommend doing that just on principle.

> Also, AutoVacOpts (used as part of reloptions) gained three extra
> fields.  Since this is in the middle of StdRdOptions, it'd be somewhat
> more involve to put these at the end of that struct.  This might be a
> problem if somebody has a module calling RelationIsSecurityView().  If
> anyone thinks we should be concerned about such an ABI change, please
> shout quickly.

That sounds problematic --- surely StdRdOptions might be something
extensions are making use of?
        regards, tom lane



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: narwhal and PGDLLIMPORT
Следующее
От: Greg Stark
Дата:
Сообщение: Re: Recovery inconsistencies, standby much larger than primary