| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC) |
| Date: | 2007-09-27 14:13:02 |
| Message-ID: | 46FB741E.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> On Thu, Sep 27, 2007 at 3:17 AM, in message
<E1539E0ED7043848906A8FF995BDA57902685E09(at)m0143(dot)s-mxs(dot)net>, "Zeugswetter
Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> wrote:
>
> The probably useful next step would be to pass the current length to the
> archive_command,
> so it can write the filled part of the file without the need for a
> filter.
I can see that helping a lot, but not by writing onto the file on disk.
If the file is nearly empty, that would be a lot of disk I/O which doesn't
need to happen. One place it could help is allowing the archive script to
skip the filter if the file is full. On files with unused space, we could
skip the rest of the input and just blast out zeros to the desired file
length.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2007-09-27 14:22:57 | Re: [FEATURE REQUEST] Streaming Onlinebackup (Maybe OFFTOPIC) |
| Previous Message | NikhilS | 2007-09-27 14:12:06 | Assertion failure due to ColumnRefStar |