Wolfgang Wilhelm wrote: > yes, indeed I'm a little confused. I'm not the only one, some Pg-Guys from other companies which I > asked about the topic were a little bit puzzled, too. > > If this is really a left over and just for portablity when will be time for a clean up? May be not for > the next years' version - there should be in good PG manner just an information that this feature is > deprecated, if the Hackers agree - but may be for the PG-version of 2017 or 2018? > > > As you as a contributor are more included in the development of PG code, do you see chances to get > that out of the code? If so I'm willing to have a look in the code whether there are comments about > that feature. Tom Lane has taken care of it before I even got to read your e-mail: http://www.postgresql.org/message-id/E1XmB2w-0008Ho-NO@xxxxxxxxxxxxxxxxxxxxxx It will be gone in 9.5. Yours, Laurenz Albe -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
