Re: BUG #1809: invalid pointer on pg_ctl reload - Mailing list pgsql-bugs

From CHRIS HOOVER
Subject Re: BUG #1809: invalid pointer on pg_ctl reload
Date
Msg-id NZ53e334-2744692e@companiongroup.com
Whole thread Raw
In response to BUG #1809: invalid pointer on pg_ctl reload  ("Chris Hoover" <chris.hoover@companiongroup.com>)
List pgsql-bugs
I was playing around and had most entries uncommented, even if I did not
change the values.  I am attaching the cleaned up postgresql.conf and my
pg_hba.conf files for you.



 Chris Hoover
Application Development System Analyst 2
Companion Technologies
8901 Farrow Rd.
Columbia, SC 29203
Phone: (803) 264-3896
E-Mail: chris.hoover@companiongroup.com
Web: http://www.companiontechnologies.com
------------------( Forwarded letter 1 follows )---------------------
Date: Mon, 08 Aug 2005 12:20:56 -0400
To: chris.hoover
Cc: pgsql-bugs@postgresql.org.comp
From: Tom.Lane[tgl]@sss.pgh.pa.us.comp
Subject: Re: [BUGS] BUG #1809: invalid pointer on pg_ctl reload

"Chris Hoover" <chris.hoover@companiongroup.com> writes:
> I was working with my pg_hba.conf file and did a pg_ctl -D <path> reload.  I
> received the following message, and postgresql shutdown.

> [postgres@edipgtst1 eedi]$ pg_ctl -D /database/data/eedi/ reload
> postmaster signaled
> [postgres@edipgtst1 eedi]$ *** glibc detected *** free(): invalid pointer:
> 0x082ced00 ***

What non-comment entries do you have in postgresql.conf?

It's also possible that the problem is being triggered by an unusual
entry in one of the other config files, such as pg_hba.conf.  Please see
if you can narrow down what's causing this.

            regards, tom lane


Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1809: invalid pointer on pg_ctl reload
Next
From: "Ian Burrell"
Date:
Subject: BUG #1814: Cancelling a CLUSTER changes the OID counter