From: | Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Using an SMP machine to make multiple indices on the |
Date: | 2001-10-23 17:59:32 |
Message-ID: | 200110231759.NAA02477@osprey.astro.umass.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom,
Yes, I understand locking the table, but empirically, two index
creations will not run simultaneously on the same table. So if
I start (and background) two
psql -c "create index one on mytable . . ." database
psql -c "create index two on mytable . . ." database
commands. The first one starts and the second one waits until the
first is finished (as tracked by "ps avx" or "top").
--Martin
Tom Lane wrote on Mon, 22 Oct 2001 23:09:26 EDT
>Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu> writes:
>> On Postgresql 7.1.3, it seems that the table is locked after the
>> first "create index" is started up. Is this right?
>
>AFAIK it's a share lock, which only prohibits modifications to the
>table, not reads (nor concurrent index builds). Not sure how you
>expect the system to do better than that.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Weinberg | 2001-10-23 18:14:30 | Re: Using an SMP machine to make multiple indices on the |
Previous Message | Doug McNaught | 2001-10-23 17:53:24 | Re: openssl & postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Studenmund | 2001-10-23 18:09:53 | Re: Proposed new create command, CREATE OPERATOR CLASS |
Previous Message | Tom Lane | 2001-10-23 17:49:36 | Re: storing binary data |