| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Sreekanth Palluru <sree4pg(at)gmail(dot)com> |
| Cc: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Re: Would like to below scenario is possible for getting page/block corruption |
| Date: | 2016-12-12 02:23:03 |
| Message-ID: | CAB7nPqQ64hjZZ4ywNNmbbpcQ9TKaF=R5hzMJGdL19PXNdSv-Lw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Sun, Dec 11, 2016 at 12:00 PM, Sreekanth Palluru <sree4pg(at)gmail(dot)com> wrote:
> I am looking at possibility of PG introducing corruption if relation extends and before it updates new page with pageheader in memory and crash happens?
>
> Is this possible?
No.
> Does PG updates pageheader when relation get extends?
You need to look at smgrextend() when extension an on-disk relation
file. The page is written in a correct shape.
> If so what details it writes? Or will it be null?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2016-12-12 06:41:36 | Re: switching replication from standard asynch to slots |
| Previous Message | Sreekanth Palluru | 2016-12-11 03:00:03 | Re: [ADMIN] Would like to below scenario is possible for getting page/block corruption |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-12-12 03:08:04 | Re: WAL history files - Pgsql 9.2 |
| Previous Message | David G. Johnston | 2016-12-12 01:42:38 | Re: huge table occupation after updates |