On Tue, Jan 17, 2012 at 1:23 PM, Noah Misch wrote:
> On Mon, Jan 16, 2012 at 08:54:53PM -0500, Robert Haas wrote:
>> On Sun, Dec 18, 2011 at 11:53 AM, Noah Misch wrote:
>> > Here's a version that calls sigsetjmp() once per file. ?While
>> > postgresql.conf
>> > scanning hardly seems like the pla
I finally had time to test this further on a variety of systems, and was
unable to reproduce on any non-Windows platform. The dump even works fine
on Windows XP; just not Windows 7.
This prompted me to do a little more research, and this time I found this
thread from Sept. 2011:
http://postgresq
"Kevin Grittner" wrote:
> Andrew Alcheyev wrote:
>
>> Well, it does good and the backend hasn't crashed yet, but the
>> client is still experiencing query problems at some point (not
>> far, I guess, from where its backend would segfault without the
>> patch). This time it encounters the follow
On Mon, Jan 16, 2012 at 08:54:53PM -0500, Robert Haas wrote:
> On Sun, Dec 18, 2011 at 11:53 AM, Noah Misch wrote:
> > Here's a version that calls sigsetjmp() once per file. ?While
> > postgresql.conf
> > scanning hardly seems like the place to be shaving cycles, this does catch
> > fatal errors
I am having the same exact problem, migrating from 8.4SS to 9.1 .
@Bruce_Momjian: Do you have a solution for this ??
I have also opened a thread for this because I didn't find this thread
before.
http://postgresql.1045698.n5.nabble.com/Upgrade-Postgres-8-4SS-gt-gt-9-1-td5151661.html
--
View
On 17 January 2012 01:37, Robert Haas wrote:
>> It's a fairly inconsequential bug, but it is worth fixing...
>
> Fixed.
Thanks.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
