Re: Segfault Exiting psql

From: Jason Essington <jasone(at)GreenRiverComputing(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Segfault Exiting psql
Date: 2006-01-27 15:21:23
Message-ID: EC943F3C-D236-458A-B5ED-FE8F81990B81@GreenRiverComputing.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Has there been any movement on this? as of 8.1.2 psql still whines on
OS X tiger when you exit.
I realize it is not significant, but I'd still rather not see it.
In the interim, I've done:

errno = 0;
write_history(fname); /* return value is not standardized */
if (errno)
psql_error("could not save history to file \"%s\": %s\n", fname,
strerror(errno));
else
return true;

and it seems to have cured the problem for me. Is this even
reasonable? I'm not a C programmer

-jason

On Aug 28, 2005, at 12:04 PM, Tom Lane wrote:

> What I'm kind of inclined to do is change our saveHistory() function
> to not look at the return value of write_history() at all, but instead
> do
>
> errno = 0;
> write_history(fname); /* return value is not standardized */
> if (errno)
> print message;
>
> Anyone have a better idea?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-27 15:26:14 Re: Logging statements and parameter values
Previous Message Joshua D. Drake 2006-01-27 15:18:42 Re: Proposal: new pg_dump options --copy-delimiter and