| From: | Jens Glaser <jens(at)helena(dot)jens(dot)de> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | reliable way to crash postgres :) |
| Date: | 1999-09-14 08:00:57 |
| Message-ID: | Pine.LNX.4.05.9909140800080.356-100000@helena.jens.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Hi,
I think I've found a pretty reliable way to crash my pgsql backend.
To reproduce (at least on 6.5.1.) enter:
select * from pg_attribute where (case when 1=1 then
(attname='testname') else (0=1) end);
I chose the pg_attribute table because it exists on every system :),
while the query does not look to make too much sense I orignally
wanted to implement different WHERE conditions based on another
condition (here just 1=1 :-)
Regards,
--
Jens Glaser Am Holderstrauch 13, 36041 Fulda, 0661/9429507 jens(at)jens(dot)de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Rison | 1999-09-14 11:02:23 | Re: [GENERAL] Getting multiple field unique index to distinguish NULLs. |
| Previous Message | Rudolph, Michael | 1999-09-14 07:27:44 | Problems with values in INSERT-Command |