| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump LOCK TABLE ONLY question |
| Date: | 2015-09-27 14:50:38 |
| Message-ID: | 2072.1443365438@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?UTF-8?Q?Filip_Rembia=C5=82kowski?= <filip(dot)rembialkowski(at)gmail(dot)com> writes:
> I'm running pg_dump constrained to one schema. It appears that pg_dump runs
> "LOCK TABLE %s IN ACCESS SHARE MODE" for each table.
> Naturally it makes sense, but...
> This schema has a table that serves as parent for thousands of child
> tables (via INHERITS).
> So effectively, to dump this schema, I have to LOCK all these tables
> not only parent.
They'd all end up locked anyway wouldn't they?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-09-27 17:56:08 | Re: Patch: Optimize memory allocation in function 'bringetbitmap' |
| Previous Message | David Rowley | 2015-09-27 12:00:03 | Re: PATCH: use foreign keys to improve join estimates v1 |