The following bug has been logged online:
Bug reference: 2678
Logged by: Jeff Trout
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: OSX 10.4.8 (Also occurs on FC4 w/kernel 2.6.16
Description:Create or replace function with OUT args
The following bug has been logged online:
Bug reference: 2678
Logged by: Jeff Trout
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: OSX 10.4.8 (Also occurs on FC4 w/kernel 2.6.16
Description:Create or replace function with OUT args
tbrokendp(12345);
commit;
\q
pg_dump broken1 > broken1.sql
createdb broken2
psql -f broken1.sql broken2
You'll see the numbers go radically different
(ie 9.375 changing to 5.39500333695425e-315)
and when you restore the backup, the getBrokenDP function will not
make a datatype complai
On Jan 24, 2007, at 12:24 PM, Tom Lane wrote:
Jeff Trout <[EMAIL PROTECTED]> writes:
I just ran across this, and I do not think it is entirely a PG bug or
even something that the backend can detect and handle.
The problem stems from swapping a table definition from under a
function.
