| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: WAL logging freezing |
| Date: | 2006-10-24 12:11:33 |
| Message-ID: | 20061024121133.GB26593@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas wrote:
> Here's a patch for WAL logging tuple freezes in vacuum, per discussion
> on pgsql-bugs.
>
> This patch is against CVS head. Should this be backported to stable
> branches? I think it should.
Keep in mind that previous releases do not use the same method for
determining the pg_clog cutoff point.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2006-10-24 12:43:20 | Re: [HACKERS] COPY does not work with regproc and aclitem |
| Previous Message | Tux P | 2006-10-24 11:54:39 | Re: PgSQL users quota |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2006-10-24 12:43:20 | Re: [HACKERS] COPY does not work with regproc and aclitem |
| Previous Message | Hitoshi Harada | 2006-10-24 09:52:01 | Re: [PATCHES] smartvacuum() instead of autovacuum |