| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: max_standby_delay considered harmful |
| Date: | 2010-05-04 14:42:29 |
| Message-ID: | 1272984149.4535.2133.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2010-05-04 at 14:49 +0100, Simon Riggs wrote:
> The only difference is that max_standby_delay is measured from log
> timestamp. Perhaps it should work from WAL receipt timestamp rather than
> from log timestamp? That would make some of the problems go away without
> significantly changing the definition. I'll look at that.
Patch to implement this idea posted in response to OT, upthread, so I
can respond to the original complaints directly.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-05-04 14:42:40 | Re: Reg: SQL Query for Postgres 8.4.3 |
| Previous Message | Pavel Stehule | 2010-05-04 14:32:48 | Re: what is good solution for support NULL inside string_to_array function? |