Re: bug in prepared statements, alter table <8.3

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: bug in prepared statements, alter table <8.3
Date: 2008-08-07 22:49:48
Message-ID: 87fxpgl9tf.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Merlin" == "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:

Merlin> postgres=# alter table abc alter a type numeric;
Merlin> ALTER TABLE
Merlin> Time: 254.847 ms
Merlin> postgres=# EXECUTE ins_abc;
Merlin> INSERT 0 1
Merlin> Time: 0.452 ms
Merlin> postgres=# select * from abc;
Merlin> ERROR: invalid memory alloc request size 18446744073709551610

Merlin> :-)

Merlin> h/t to rhodium toad.

This is fairly obviously a simple consequence of the lack of plan
invalidation, it just happens to be more serious than most (you can,
as a normal user, break the backend in a dozen different ways, from
bad data or incomprehensible error messages up through SEGVs).

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-07 23:56:18 Re: patch: Add columns via CREATE OR REPLACE VIEW
Previous Message Robert Haas 2008-08-07 22:38:04 Re: patch: Add columns via CREATE OR REPLACE VIEW