As it turns out, it was prepared transactions at fault. I restored my test
bed, forced a rollback and the locks were gone. At least now I can connect
those dots. :-)
On Fri, Feb 22, 2013 at 1:15 AM, Albe Laurenz wrote:
> Ned Wolpert wrote:
> > I'm doing a postmortem on a corru
My bad, I'll re-post this to pgsql-general with more data on my running
environment
On Thu, Feb 21, 2013 at 11:16 AM, Ned Wolpert wrote:
> Folks-
>
> I'm doing a postmortem on a corruption event we had. I have an idea on
> what happened, but not sure. I figure I
n we
killed that app server? Or am I looking in the wrong place.
I do still have the old data directories so I can start them up and check
out the dataset. Any advice?
--
Virtually, Ned Wolpert
"Settle thy studies, Faustus, and begin..." --Marlowe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is one bet I'm glad to lose. :-)
Alvaro Herrera wrote:
> Ned Wolpert escribió:
>
>> In my current production environment, the PostgreSQL database server
>> is the latest, 8.2.4. The apps that communicate with it are plan
On 7/12/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Don't use a mismatching psql version with the server version.
--
Virtually, Ned Wolpert
http://www.codeheadsystems.com/blog/
"Settle thy studies, Faustus, and begin..." --Marlowe
---(end of br
