From: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: GUC vs variable.c (was Patches applied...) |
Date: | 2002-04-21 23:22:40 |
Message-ID: | 3CC349C0.8AF58951@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
...
> regression=# set seed to 1,2;
> server closed the connection unexpectedly
> (crash is due to assert failure)
Now that I look, the assert is one I put in explicitly to catch multiple
arguments! I wasn't sure what the behavior *should* be, though I could
have done worse than simply checking for multiple arguments and throwing
a more graceful elog(ERROR) with a message about having too many
arguments to SET SEED...
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2002-04-21 23:36:44 | Re: GUC vs variable.c (was Patches applied...) |
Previous Message | Thomas Lockhart | 2002-04-21 22:32:30 | Re: GUC vs variable.c (was Patches applied...) |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2002-04-21 23:36:44 | Re: GUC vs variable.c (was Patches applied...) |
Previous Message | Tom Lane | 2002-04-21 23:05:35 | Re: Coster/planner and edge cases... |