| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Subject: | No more need for pg_clearxlogtail? |
| Date: | 2013-08-02 04:20:15 |
| Message-ID: | 20130802042015.GA4174@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Jul 8, 2013 at 09:16:32AM +0000, Heikki Linnakangas wrote:
> This has one user-visible change: switching to a new WAL segment with
> pg_switch_xlog() now fills the remaining unused portion of the segment with
> zeros. This potentially adds some overhead, but it has been a very common
> practice by DBA's to clear the "tail" of the segment with an external
> pg_clearxlogtail utility anyway, to make the WAL files compress better.
> With this patch, it's no longer necessary to do that.
So this removes the need to add pg_clearxlogtail to contrib? Great.
Thanks.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-02 04:45:24 | pgsql: pg_test_fsync: expand ops/sec display |
| Previous Message | Stephen Frost | 2013-08-01 19:44:18 | pgsql: Improve handling of pthread_mutex_lock error case |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-08-02 04:35:36 | Re: Regarding BGworkers |
| Previous Message | Alvaro Herrera | 2013-08-02 04:13:05 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |