| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Bruce Momjian <bruce(at)momjian(dot)us>, fgp(at)phlo(dot)org, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Error code for "terminating connection due to conflict with recovery" |
| Date: | 2011-02-01 06:35:25 |
| Message-ID: | AANLkTikJCXnAMb7ByuAOXrxW2D584xWnDSFeMBsZ0t4+@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 1, 2011 at 03:29, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Jan 31, 2011 at 8:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Then again - in theory, there's no reason why we couldn't drop a
>>> database on the master when it's in use, kicking out everyone using it
>>> with this very same error code. We don't happen to handle it that way
>>> right now, but...
>>
>> Yeah, that was in the back of my mind too. "DROP DATABASE foo FORCE",
>> maybe?
>
> I have to think some people would find that useful.
Yes.
If nothing else, it would save some typing :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-02-01 06:46:30 | Re: bad links in messages from commits |
| Previous Message | Itagaki Takahiro | 2011-02-01 06:00:23 | Re: off-by-one mistake in array code error reporting |