| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Greg Rychlewski (LCL)" <Greg(dot)Rychlewski(at)loblaw(dot)ca> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: "Create index" lock type |
| Date: | 2020-07-15 01:34:02 |
| Message-ID: | CAKFQuwandQ-4pjUwKds+kk87x7LH3EfeyNncpvjG3xb0_0kvLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Tuesday, July 14, 2020, Greg Rychlewski (LCL) <Greg(dot)Rychlewski(at)loblaw(dot)ca>
wrote:
> What kind of lock does the “create index” (not concurrent) command take?
> From the documentation, it says that it blocks out writes. But I’m not sure
> how to find the exact lock type in the documentation.
>
>
>
> The reason I’m asking is because I’m trying to see if it conflicts with
> the lock taken by autovacuum (to prevent wraparound), “SHARE UPDATE
> EXCLUSIVE”.
>
> Share
https://www.postgresql.org/docs/12/explicit-locking.html#LOCKING-TABLES
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devraj B | 2020-07-15 03:42:20 | How to connect PostgreSQL (9.6.17) database from Macbook Pro Terminal using JumpCloud password? |
| Previous Message | Greg Rychlewski (LCL) | 2020-07-15 00:57:55 | "Create index" lock type |