| From: | "Aaron Bono" <postgresql(at)aranya(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: truncate partitioned table locking |
| Date: | 2006-06-19 20:02:48 |
| Message-ID: | bf05e51c0606191302h25a967denf90d232f83ccc30f@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I am curious, why would a query on a parent table, A, put a lock on a child
table, B? If the query doesn't touch B or any of its children, why would
PostgreSQL care what happens to the child table during its query?
-Aaron
On 6/19/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> > I have master table A, inherited by Table B and Table C
>
> > Does the truncation of a child table take a lock on the master table ?
>
> No, but it certainly locks the child table ... and queries on A are
> going to try to scan all three tables.
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-20 01:24:08 | Re: truncate partitioned table locking |
| Previous Message | Sriram Dandapani | 2006-06-19 19:50:23 | Re: truncate partitioned table locking |