| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Greg Smith <gsmith(at)gregsmith(dot)com>, Kyle Cordes <kyle(at)kylecordes(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improving compressibility of WAL files |
| Date: | 2009-01-09 18:22:43 |
| Message-ID: | 27818.1231525363@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Yes, we could make the archiver do this, but I see no big advantage over
> having it done externally. It's not faster, safer, easier. Not easier
> because we would want a parameter to turn it off when not wanted.
And the other question to ask is how much effort and code should we be
putting into the concept anyway. AFAICS, file-at-a-time WAL shipping
is a stopgap implementation that will be dead as a doornail once the
current efforts towards realtime replication are finished. There will
still be some use for forced log switches in connection with backups,
but that's not going to occur often enough to be important to optimize.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reg Me Please | 2009-01-09 18:49:58 | Re: [EXPLAIN] Nested loops |
| Previous Message | Victor Nawothnig | 2009-01-09 18:22:28 | Re: [EXPLAIN] Nested loops |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-01-09 18:27:14 | Re: Solve a problem of LC_TIME of windows. |
| Previous Message | Richard Huxton | 2009-01-09 17:59:43 | Re: Improving compressibility of WAL files |