"utsav" <utsav.tur...@newgen.co.in> writes:
> I am using postgres 7.3. on RHEL 4.0
7.3.what? If it's not 7.3.21 then an update would probably be worth
your time. In particular there were fixes in 7.3.14 and 7.3.20 that
could possibly explain this.
If it is 7.3.21, then I think an upgrade to a newer major release series
is your only hope of getting a fix. The PG community declared 7.3.x to
be EOL nearly two years ago, and I believe that Red Hat's policy is
they'll only consider fixing security bugs in it at this point. Which
this is not.
If you can demonstrate the same type of failure in a currently supported
release, we'd take more of an interest, but fixing 7.3 isn't going to
happen :-(
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
