| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WALInsertLock tuning |
| Date: | 2011-06-07 12:54:11 |
| Message-ID: | BANLkTimM_dDw6LpRy-5vWoEqJxzxTwvDHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 7, 2011 at 1:24 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> One other thought is that I think that this patch might cause a
> user-visible behavior change. Right now, when you hit the end of
> recovery, you most typically get a message saying - record with zero
> length. Not always, but often. If we adopt this approach, you'll get
> a wider variety of error messages there, depending on exactly how the
> new record fails validation. I dunno if that's important to be worth
> caring about, or not.
Not.
We've never said what the message would be, only that it would fail.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-07 12:59:34 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Previous Message | Kevin Grittner | 2011-06-07 12:36:26 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |