Horton

Re: pgpool versus sequences

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: tgl <tgl@sss.pgh.pa.us>, robertmhaas <robertmhaas@gmail.com>, mangoo <mangoo@wpkg.org>, scott.marlowe <scott.marlowe@gmail.com>, Kevin.Grittner <kevin.grittner@wicourts.gov>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-01T23:47:06Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Rearrange ALTER TABLE syntax processing as per my recent proposal: the

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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support