Uh, do you have a password configured for the super-user? Could that be
the prompt?
---
Daniel Alvarez wrote:
> PostgreSQL 7.2.1 / SUSE Linux 8.0
>
> According to the output of "pg_ctl --help", the -w option (lowercase)
>
Looks like an ODBC error. Is it? Have you tried the newest odbc at
odbc.postgresq.org?
---
Niranjan Shivaratri wrote:
> I am running postgres 7.1 version on a Mips platform running Linux (2.4.17sb20020611
>version).
> T
The attached patch fixes 'Bad Timestamp format' exception when timestamp value is
'ininity' or '-ininity'.
I hope, it helps...
Dima.
Index: AbstractJdbc1ResultSet.java
===
RCS file:
/projects/cvsroot/pgsql/src/interfaces/jdbc/org/
Donald Fraser ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
timestamp is converted to timestamptz
Long Description
When specifying a column data type as timestamp it is always converted to timestamptz.
According to the docume
Pg 104 of "A Guide to THE SQL STANDARD" Fourth Edition by Date/Darwen says:
...
2. Observe that the definition makes no mention of row ordering. As
explained in Chapter 2, the rows of an SQL table have no ordering (and the
same is true of true relational tables). It is possible, as we will see in
I send a simple patch for PL/pgSQL parser which allow now to use whitespaces
in identifers of any kind(table names,attribute names,variables ...) in Pl/pgSQL
procedural language.Explicit definition of bug can be found in
Re: [HACKERS] Bug of PL/pgSQL parser
plpgsql.dquote.patch
Desc