| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | tgl <tgl(at)sss(dot)pgh(dot)pa(dot)us>, robertmhaas <robertmhaas(at)gmail(dot)com>, mangoo <mangoo(at)wpkg(dot)org>, scott(dot)marlowe <scott(dot)marlowe(at)gmail(dot)com>, Kevin(dot)Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgpool versus sequences |
| Date: | 2011-06-01 23:47:06 |
| Message-ID: | 1306971997-sup-5549@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Excerpts from Tatsuo Ishii's message of mié jun 01 19:08:16 -0400 2011:
> What pgpool really wanted to do was locking sequence tables, not
> locking rows in sequences. I wonder why the former is not allowed.
Yeah -- why is LOCK SEQUENCE foo_seq not allowed? Seems a simple thing
to have.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-02 00:02:09 | Re: pgpool versus sequences |
| Previous Message | Tatsuo Ishii | 2011-06-01 23:26:39 | Re: pgpool versus sequences |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2011-06-01 23:48:44 | Re: creating CHECK constraints as NOT VALID |
| Previous Message | Mark Kirkwood | 2011-06-01 23:35:55 | Re: patch review : Add ability to constrain backend temporary file space |