Bug #478: Integer overflow in pg_dump - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #478: Integer overflow in pg_dump
Date
Msg-id 200110111037.f9BAbiV01460@postgresql.org
Whole thread Raw
Responses Re: Bug #478: Integer overflow in pg_dump  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Premysl Maly (premek.maly@seznam.cz) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Integer overflow in pg_dump

Long Description
Talking about version pg_dump  (7.1.3)


Well, it fails, when dumping databases indices (while dumping comment on indexes). I hacked the source code and found
theselect which failed. It is on line 3036 of file pg_dump. 

The select looks like:

SELECT description FROM pg_description where oid = 4294958683

it fails always with dtoi4: Integer out of range

I hacked a source, so now the searched oid is qouted:

SELECT description FROM pg_description where oid = '4294958683'

and the bug is gone. Please in a new release look at that. Large numbers should be qouted otherwise they kill SELECT
query.

See you

Premek


Sample Code

in pg_dump source on lines 3036-7 should be:

appendPQExpBuffer(query, "SELECT description FROM pg_description where oid = '");
appendPQExpBuffer(query,oid); appendPQExpBuffer(query,"'");

instead of

appendPQExpBuffer(query, "SELECT description FROM pg_description where oid = ");
appendPQExpBuffer(query,oid);



No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: SQLPutData bug ?
Next
From: Bruce Momjian
Date:
Subject: Re: Bug #463: Make 'infinity' work with type 'date'