On Mon, 3 Nov 2003, Tom Lane wrote:
> Martin Edlman <[EMAIL PROTECTED]> writes:
> > [ unstable index behavior ]
>
> I'm wondering about hardware problems --- how sure are you that you
> don't have flaky RAM or a bad disk drive?
I'll check this, the RAID controller reports this. RAM should be OK.
Patch Applied,
Thanks,
Dave
On Mon, 2003-11-03 at 05:25, Kris Jurka wrote:
> On Fri, 15 Aug 2003, Richard Froud wrote:
>
> > Please enter a FULL description of your problem:
> >
> > When reading database metadata for foreign keys using the JDBC
>
Patch Applied,
Thanks,
Dave
On Mon, 2003-11-03 at 04:45, Kris Jurka wrote:
> Half of this bug was fixed at some point, but an exception is still thrown
> when calling rs.afterLast() and then rs.previous(). Attached is a
> regression test addition and the appropriate fix. Sorry for the extreme
>
"" <[EMAIL PROTECTED]> writes:
> With the help of two people from #postgresql at irc.freenode.org, I did a
> initdb -d --pgdata data 2>debug.log and founded out that the problem was that
> conversion_create.sql wasn't changing $libdir to the actual name
It's not supposed to. I don't know what pr
Martin Edlman <[EMAIL PROTECTED]> writes:
> [ unstable index behavior ]
I'm wondering about hardware problems --- how sure are you that you
don't have flaky RAM or a bad disk drive?
Also, what locale settings are you using in the database (use
pg_controldata to verify this)? It seems possible th
Hello,
I had a problem with PostgreSQL 7.3.4, the pg_conversion table was empty after
initdb, so, no conversion could be made. I did exactly this:
# tar xvzf postgres-7.3.4.tar.gz
# cd postgres-7.3.4
# ./configure --prefix=/var/lib/pgsql --with-java --with-openssl
--without-readline
# make
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have encountered serious problem with PostgreSQL 7.3.4, the same
with previous version 7.3.2 (installed from RPMs postgresql-7.3.4-1PGDG)
running on dual processor machine. Maybe dual processors cause described
problems but I suppo
On Fri, 15 Aug 2003, Richard Froud wrote:
> Please enter a FULL description of your problem:
>
> When reading database metadata for foreign keys using the JDBC
> DatabaseMetaData.getImportedKeys() and DatabaseMetaData.getExportedKeys()
> methods t
Half of this bug was fixed at some point, but an exception is still thrown
when calling rs.afterLast() and then rs.previous(). Attached is a
regression test addition and the appropriate fix. Sorry for the extreme
delay in response and thanks for the thorough report.
Kris Jurka
On Fri, 24 Jan
