Tom Lane wrote:
> According to that, Linux keepalive starts working once you have either
> sent or received at least one byte over the connection. Therefore it's
> not possible to get past the authentication stage without keepalive
> being ready to go. And we do have a pretty short timeout on the
Fujii Masao <[EMAIL PROTECTED]> writes:
> Because 'idle in transaction' backends that don't terminate by tcp_keepalive
> keep holding the lock.
If a backend has gotten to the point of being 'idle in transaction',
then it's certainly exchanged data with the client, so TCP keepalive
should work. I
The following bug has been logged online:
Bug reference: 2585
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: GNU/Linux
Description:Please provide pkg-config support
Details:
I haven't found a suitable place to put this wish-
Hi,
I found a minor glitch in the documentation for 8.1 where it talks about
boolean data type.
Here is what the documentation says:
"Tip: Values of the boolean type cannot be cast directly to other types
(e.g., CAST (boolval AS integer) does not work)."
It is true for pre-8.1. As for 8.1, ho
The following bug has been logged online:
Bug reference: 2586
Logged by: Sunil Kumar Basu
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:Connecting problem
Details:
Hi,
I am getting connected to the PostgreSQL datab
[EMAIL PROTECTED] wrote:
> The following bug has been logged online:
>
> Bug reference: 2585
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system: GNU/Linux
> Description:Please provide pkg-config support
> Details:
>
> I ha
> The following bug has been logged online:
>
> Bug reference: 2586
> Logged by: Sunil Kumar Basu
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows XP
> Description:Connecting problem
> Details:
>
> Hi,
> I am getting connected t
Tom,
> This is documented behavior for arrays:
> http://developer.postgresql.org/docs/postgres/arrays.html#AEN5764
> and has been that way for a very long time. If we change it we will
> break every array-using application on the planet, because it will
> in fact be impossible to parse an array v
Hello Tom,
in June I've complained about a 'failed to fetch new tuple for AFTER
trigger' error and you requested a test case here:
http://archives.postgresql.org/pgsql-general/2006-07/msg00855.php
I finally got around to strip down the problem. The error first occurred
to me using a 8.2devel
Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> CREATE TABLE category (
> id INT PRIMARY KEY,
> name TEXT);
> CREATE TABLE category_todo (
> cat_id INT REFERENCES category(id)
> DEFERRABLE INITIALLY DEFERRED
> );
> BEGIN;
> INSERT INTO category (id, name) VALUES (0, 'te
On Mon, 21 Aug 2006, Tom Lane wrote:
> Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> > CREATE TABLE category (
> > id INT PRIMARY KEY,
> > name TEXT);
>
> > CREATE TABLE category_todo (
> > cat_id INT REFERENCES category(id)
> > DEFERRABLE INITIALLY DEFERRED
> > );
>
>
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Yeah, I think there are a few possibilities around truncate inside a
> savepoint that's rolledback that we have to be careful of.
Yuck :-(
> If we could mark the entries in some way so we knew whether or not they
> were made obsolete by a truncate of ou
On Mon, 21 Aug 2006, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Yeah, I think there are a few possibilities around truncate inside a
> > savepoint that's rolledback that we have to be careful of.
>
> Yuck :-(
>
> > If we could mark the entries in some way so we knew whether o
Tom Lane wrote:
> "Rae Stiening" <[EMAIL PROTECTED]> writes:
> > Description of the "width_bucket(...)"
>
> > "return the bucket to which operand would be assigned in an equidepth
> > histogram with count buckets, an upper bound of b1, and a lower bound of
> > b2"
>
> > I believe that the lower b
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Eu
15 matches
Mail list logo
