Re: psql SET/RESET/SHOW tab completion - Mailing list pgsql-hackers

From Michael Fuhr
Subject Re: psql SET/RESET/SHOW tab completion
Date
Msg-id 20050813170418.GA96026@winnie.fuhr.org
Whole thread Raw
In response to Re: psql SET/RESET/SHOW tab completion  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql SET/RESET/SHOW tab completion  (Michael Fuhr <mike@fuhr.org>)
List pgsql-hackers
On Sat, Aug 13, 2005 at 12:41:51PM -0400, Tom Lane wrote:
> Michael Fuhr <mike@fuhr.org> writes:
> > Is 162 a typo or are you working on something that hasn't been
> > committed yet?  I see 161 in the latest code.
> 
> Uh, I get 162 ... and no I don't have any uncommitted changes ATM.

I found the difference: one of my boxes is missing debug_assertions.
I had removed --enable-cassert from my configure script while doing
some performance tests and never put it back (I had noticed that
VACUUM was quite slow on that box and found that it was due to the
assertion checks).

-- 
Michael Fuhr


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: SPI: ERROR: no snapshot has been set
Next
From: Tom Lane
Date:
Subject: Re: psql SET/RESET/SHOW tab completion