From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, 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-02 15:10:00 |
Message-ID: | 15726.1307027400@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of jue jun 02 10:31:58 -0400 2011:
>> That's a lot of work for a purely cosmetic issue, though. What would be
>> trivial is to let this work:
>> regression=# lock table s1;
>> ERROR: "s1" is not a table
> Yeah, though it'd be nice to avoid this:
> alvherre=# create schema public_too;
> CREATE SCHEMA
> alvherre=# set search_path to 'public_too', 'public';
> SET
> alvherre=# create table public_too.s1 ();
> CREATE TABLE
> alvherre=# create sequence public.s1;
> CREATE SEQUENCE
> alvherre=# begin;
> BEGIN
> alvherre=# lock s1;
> LOCK TABLE
> At this point we have a lock on the table, but if we change LOCK to also
> look for sequences, the behavior would change.
No it wouldn't. You seem to be imagining that sequences live in a
different namespace from tables, but they don't. There can only be one
relation that "s1" will refer to for any search_path setting.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-06-02 15:27:43 | Re: pgpool versus sequences |
Previous Message | Alvaro Herrera | 2011-06-02 14:55:26 | Re: pgpool versus sequences |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-06-02 15:12:08 | Re: BLOB support |
Previous Message | Pavel Golub | 2011-06-02 15:07:30 | Re: [HACKERS] PQdeleteTuple function in libpq |