| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4 |
| Date: | 2010-03-13 21:24:08 |
| Message-ID: | 1268515448.3825.4304.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Sat, 2010-03-13 at 11:29 -0800, Josh Berkus wrote:
> > That's better, I was worried you'd gone all complimentary on me.
>
> <grin>Never fear that!
>
> Was that setting originally part of your design for HS? If so, why did
> you back off from it?
We all agreed its a kluge, that's why.
It's also my 3rd choice of solution behind fine-grained lock conflicts
(1st) which would avoid many issues and master/standby in lock step
(2nd).
Having said that I'm much in favour of providing a range of options and
then letting users tell us what works for them.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-03-13 22:02:21 | Re: BUG #5362: WARNING could not determine encoding |
| Previous Message | Josh Berkus | 2010-03-13 19:29:49 | Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-03-13 23:29:54 | Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4 |
| Previous Message | Jaime Casanova | 2010-03-13 20:15:06 | Re: pq_setkeepalives* functions |