Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> What is a "-601 error"? There's surely no such message in Postgres.
> There surely is in ecpg:
> ecpgerrno.h:#define ECPG_WARNING_QUERY_IGNORED -601
Hmm ... maybe, but a query-ignored failure could only happen in the
case of multiple comm
Casey Allen Shobe <[EMAIL PROTECTED]> writes:
> Tabs should paste; they're normal characters.
Turn off readline (psql -n). For someone accustomed to tab completion,
the above is about as sensible as demanding we disable backspace.
It would be nice if we could distinguish pasted tabs from manual
Let's say I have typed a nice formatted SQL statement like so:
select b1.blah,
b1.blah2,
b2.blah3
fromblah_table as b1
inner join only blah_table2 as b2
on b1.blah = b2.blah;
...using tabs as the indenting medium. Now I copy that
I am able to use plaintext passwords + non-ssl-enabled tcp
I am able to use MD5 passwords + non-ssl-enabled tcp
I am able to use plaintext passwords + ssl-enabled tcp
I am not able to use MD5 passwords + ssl-enabled tcp. I always get a password
failure.
The server is Linux From Scratch. the cl
> > A user was setup and had GRANT permissions on individual tables in a database.
>After the user was dropped, using the /z from psql command line showed the user ID
>still existing in the individual table permissions. After the drop, several other
>users then were unable to execute SELECT o
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Could you supply a patch?
Seems to be fixed already; at least INT8 is treated differently from
INT4 in CVS tip...
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9'
Could you supply a patch?
---
[EMAIL PROTECTED] wrote:
> Ragnar Kjørstad ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> python interface doesn't
[EMAIL PROTECTED] writes:
> Summarized:
> timefield > 'now'::datetime --> NO index
> timefield > 'now'::timestamp --> index is used (OK)
"datetime" is an obsolete type name that will go away entirely in 7.3,
so I cannot get very excited about this. But I believe the issue is
that "timestamp"
John Zero ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
PostgreSQL doesn't use indexes right sometimes
Long Description
There's a field in our database of type 'timestamp with time zone'.
We have on index on this field.
When
[EMAIL PROTECTED] writes:
> A user was setup and had GRANT permissions on individual tables in a database.
>After the user was dropped, using the /z from psql command line showed the user ID
>still existing in the individual table permissions. After the drop, several other
>users then were un
Mickey Parker ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Drop user damages security on tables
Long Description
A user was setup and had GRANT permissions on individual tables in a database. After
the user was dropped, us
11 matches
Mail list logo
