Re: psql SET/RESET/SHOW tab completion

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql SET/RESET/SHOW tab completion
Date: 2005-08-13 17:05:27
Message-ID: 14197.1123952727@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Michael Fuhr <mike(at)fuhr(dot)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.

Oh, I bet I know what it is: I built with --enable-cassert which
creates "debug_assertions" as a GUC variable.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-08-13 17:09:34 Re: SPI: ERROR: no snapshot has been set
Previous Message Michael Fuhr 2005-08-13 17:04:18 Re: psql SET/RESET/SHOW tab completion