| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, mangoo(at)wpkg(dot)org, scott(dot)marlowe(at)gmail(dot)com, t-ishii(at)sra(dot)co(dot)jp, Kevin(dot)Grittner(at)wicourts(dot)gov, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgpool versus sequences |
| Date: | 2011-06-02 19:54:30 |
| Message-ID: | 27667.1307044470@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jun 1, 2011 at 6:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Please note also that what pgpool users have got right now is a time
>> bomb, which is not better than immediately-visible breakage. I would
>> prefer to try to get this change out ahead of widespread adoption of the
>> broken pgpool version.
> Hmm, I gather from what Tatsuo is saying at the web site that this has
> only been broken since the release of 3.0 on February 23rd, so given
> that I think your approach makes sense.
Done, and I also installed a kluge to clean up the damage retroactively
during any nextval/setval operation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | fel | 2011-06-03 10:22:31 | - upgrade advice |
| Previous Message | Kevin Grittner | 2011-06-02 17:47:16 | Re: Problem with postgres 8.2.5 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-06-02 20:21:08 | Re: BLOB support |
| Previous Message | Tom Lane | 2011-06-02 19:49:53 | Re: Estimating total amount of shared memory required by postmaster |