| From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alex Shulgin <alex(dot)shulgin(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: In which catalog postgres Instance Crash time recorded ? |
| Date: | 2011-11-23 17:01:50 |
| Message-ID: | CA+h6Ahi7XO_tuDo9gdtexb0SP+st6WqkDaURNDB_f=ikQb6p1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 23, 2011 at 10:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> writes:
> > On Wed, Nov 23, 2011 at 9:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> No, it's looking at a last-update timestamp field in pg_control.
>
> > So, Is it a approximate time of crash on the basis of last-modified
> > timestamp of pg_control file ?
>
> IIRC, that's going to be the time of last checkpoint completion on a
> normally-operating server. So depending on your checkpoint settings,
> and how busy the server is, it might or might not be very close to
> the time of crash.
>
> regards, tom lane
>
Perfect. I understood.
Thanks for explaining Tom... :)
---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris McDonald | 2011-11-23 18:04:14 | plpgsql Difference in behaviour between versions? |
| Previous Message | Tom Lane | 2011-11-23 16:57:24 | Re: In which catalog postgres Instance Crash time recorded ? |