| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Command to prune archive at restartpoints |
| Date: | 2010-06-08 22:45:19 |
| Message-ID: | 12017.1276037119@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I prefer archive_cleanup_command. We should name things after their
> principal function, not an implementation detail, IMNSHO.
Weak preference for archive_cleanup_command here.
> More importantly, we should include an example in the docs. I created
> one the other day when this was actually bothering me a bit (see
> <http://people.planetpostgresql.org/andrew/index.php?/archives/85-Keeping-a-hot-standby-log-archive-clean.html>).
> That seemed to work ok, but maybe it's too long, and maybe people would
> prefer a shell script to perl.
Short is good. Maybe you could remove the logging stuff from the
example.
As for the language choice, my first thought is +1 for perl over shell,
mainly because it might be directly useful to people on Windows while
shell never would be. On the other hand, if it's possible to do a
useful one-liner in shell then let's do it that way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-06-08 23:07:05 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
| Previous Message | Tom Lane | 2010-06-08 22:35:00 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |