Re: Performance of COPY for Archive operations
Tom Lane <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.win32 |
|---|---|
| Message-ID | <[email protected]> |
"Simon Riggs" <[email protected]> writes: > Nothing that surprising there, though I think I would like to put a WARNING > message into the Archiver that triggers if more than CHECKPOINT_SEGMENTS WAL > files are ready to archive at any one time. Though maybe that would cause > more problems than it would solve: "Archiving of transaction logs cannot > keep up with system activity. If this occurs regularly, you should > reconsider your database-disk layout" Can't see the value of this. The problem will be readily apparent from growth of the pg_xlog directory --- anyone who doesn't notice that probably isn't perusing the postmaster log either. Also, once it starts to bleat, what's going to make it stop? Filling the disk with warning messages won't be a constructive improvement on the situation :-( regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [email protected] so that your message can get through to the mailing list cleanly