| From: | Maksim Milyutin <m(dot)milyutin(at)postgrespro(dot)ru> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Partitioned tables and relfilenode |
| Date: | 2017-03-23 14:27:14 |
| Message-ID: | 5c1adf61-3293-1365-e31c-b6f672446c73@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
I have noticed that there is scheduled unlinking of nonexistent physical
storage under partitioned table when we execute DROP TABLE statement on
this partitioned table. Though this action doesn't generate any error
under typical behavior of postgres because the error of storage's lack
is caught through if-statement [1] I think it is not safe.
My patch fixes this issue.
1. src/backend/storage/smgr/md.c:1385
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| exclude_unlinking_storage_for_partitioned_table.patch | text/x-patch | 519 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-23 14:34:53 | Schedule and Release Management Team for PG10 |
| Previous Message | Petr Jelinek | 2017-03-23 14:25:14 | Re: pgsql: Logical replication support for initial data copy |