| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: WAL logging freezing |
| Date: | 2006-10-27 15:44:52 |
| Message-ID: | 45422974.6010109@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> I would've liked to give freezing a new opcode,
>> but we've ran out of them (see htup.h).
>
> Hardly ... we have plenty of unused rmgr id's still.
Good point.
> The real issue that still has to be resolved is the interaction of all
> this stuff with PITR scenarios --- is it still safe to not log hint-bit
> updates when PITR is on? I think it's premature to start writing
> patches until we've decided how this really needs to work.
Not logging hint-bit updates seems safe to me. As long as we have the
clog, the hint-bit is just a hint. The problem with freezing is that
after freezing tuples, the corresponding clog page can go away.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-27 16:01:12 | Re: WAL logging freezing |
| Previous Message | Neil Conway | 2006-10-27 15:10:59 | Re: bug in on_error_rollback !? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-27 16:01:12 | Re: WAL logging freezing |
| Previous Message | Neil Conway | 2006-10-27 14:56:43 | Re: GUC description cleanup |