Not waiting for this, I've just removed the incorrect instructions.
Josh told me on Friday that he would apply a fix this weekend, but at
this point he can restore the patch and fix it if he wants.
If magnus already fixed it, I don't see why I need to fix it again ...
--
Josh Berkus
plpython: Add SPI cursor support
Add a function plpy.cursor that is similar to plpy.execute but uses an
SPI cursor to avoid fetching the entire result set into memory.
Jan UrbaĆski, reviewed by Steve Singer
Branch
--
master
Details
---
Peter Eisentraut wrote:
plpython: Add SPI cursor support
Add a function plpy.cursor that is similar to plpy.execute but uses an
SPI cursor to avoid fetching the entire result set into memory.
Jan Urba?ski, reviewed by Steve Singer
I assume this is _not_ related to this TODO item:
Remove troublesome Asserts in cost_mergejoin().
While logically correct, these two Asserts could fail depending on the
vagaries of floating-point arithmetic. In particular, on machines with
floating-point registers wider than standard double values, it was
possible for the compiler to compare a
In pg_upgrade, allow tables using regclass to be upgraded because we
preserve pg_class oids since PG 9.0.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/0e8f6bf0e7a280749cc09715acc2b27d17e1b2fd
Modified Files
--
contrib/pg_upgrade/check.c | 20
In pg_upgrade, allow tables using regclass to be upgraded because we
preserve pg_class oids since PG 9.0.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/ec218056feb4533932bce4af820523829d831f92
Modified Files
--
contrib/pg_upgrade/check.c |2
In pg_upgrade, allow tables using regclass to be upgraded because we
preserve pg_class oids since PG 9.0.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/98fbce09316525e1da5a5c94ea8d75ead69669fb
Modified Files
--
contrib/pg_upgrade/check.c |2