| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Joshua Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: Feature Request: pg_replication_master() |
| Date: | 2012-12-21 14:25:47 |
| Message-ID: | CA+U5nMJsMVnKyOmBm0C_=+gGVuMDa=K6r4w-sT+1pARVM8XQKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg메이저 토토 사이트SQL |
On 20 December 2012 19:29, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> At this point backward compatibility has paralized us from fixing a
> recovery.conf API that everyone agrees is non-optimal, and this has
> gone on for multiple major releases. I don't care what we have to do,
> just clean this up for 9.3!
The main stall at this point is that the developer who wrote that
patch no longer spends much time working on Postgres. AFAICS there is
nobody working on this for 9.3 mainly because its not a priority, nor
will implementing that fix the OP's request.
There is no paralysis because there never was a blocker, only a
request for backwards compatibility, which is easily possible to
implement.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-12-21 14:33:16 | Re: Review of Row Level Security |
| Previous Message | Simon Riggs | 2012-12-21 14:21:00 | Re: Feature Request: pg_replication_master() |