Re: pg_dump -X - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump -X
Date
Msg-id AANLkTimionrBcW2WSF+jEnvKwozOL4cceiRUOxaiQ5Nv@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump -X  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Mar 14, 2011 at 9:56 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sat, Mar 12, 2011 at 12:56 AM, Bruce Momjian <bruce@momjian.us> wrote:
>>> Presumably the point of deprecating the feature is that we'd
>>> eventually remove it.  If 4 major releases isn't long enough, what is?
>>
>> Good point.
>
> Unless there are further objections, I think we should go ahead and remove this.
>
> If there ARE further objections, then please say what release you
> think it would be OK to remove it in, or why you think it's worth
> keeping around indefinitely given that the last version in which it
> was documented is now EOL.

Hearing no further objections, I have removed this code.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.