On Fri, Aug 7, 2009 at 7:50 AM, psqluser wrote:
> I am getting the below error repeatedly in postgres 8.3
>
> 2009-08-07 15:19:35.749 ISTLOG: unexpected EOF on client connection
> 2009-08-07 15:31:47.718 ISTWARNING: worker took too long to start;
> cancelled
> 2009-08-07 15:32:22.825 ISTWARNING:
"Ian Turner" writes:
> The following queries are equivalent, because there are no integers between
> 5 and 6 and because the BETWEEN operator contemplates a closed range.
> SELECT * FROM example WHERE pk IN (5,6);
> SELECT * FROM example WHERE pk BETWEEN 5 AND 6;
The planner intentionally does no
The following bug has been logged online:
Bug reference: 4974
Logged by: Ian Turner
Email address: ian.tur...@deshaw.com
PostgreSQL version: 8.3
Operating system: Ubuntu 8.10
Description:Equivalent of "= ANY" and "BETWEEN" not observed by
planner.
Details:
Consider
2009/8/11 Tom Lane :
> Anyway it's looking like a slightly nontrivial project. Maybe we should
> just rephrase the error message Hubert is complaining about.
>
Yeah, I can't think of any simple way of distinguishing the 2 error
conditions in that code. Perhaps adding a suitable hint would help, a
On Tuesday 11 August 2009 19:00:30 Tom Lane wrote:
> I wrote:
> > Dean Rasheed writes:
> >> [The reason is that it actually searches for the trigger enforcing the
> >> constraint, and there isn't one if it's not deferrable. So the current
> >> code can't distinguish between a non-existent unique c
I wrote:
> Dean Rasheed writes:
>> [The reason is that it actually searches for the trigger enforcing the
>> constraint, and there isn't one if it's not deferrable. So the current
>> code can't distinguish between a non-existent unique constraint and a
>> non-deferrable one.]
> Yeah. Is it worth
Dean Rasheed writes:
> The constraint needs to be declared DEFERRABLE before you can defer
> it, but yes, I agree this is not a helpful error message.
> [The reason is that it actually searches for the trigger enforcing the
> constraint, and there isn't one if it's not deferrable. So the current
Platform: Windows XP, 5.1 (Build 2600).Language: Russain.
Distribution used: Binary.
pgAdmin version: 1.10.0.
PostgreSQL version: 8.4.0-1.
Bug description: When I use pgAdmin's menu command 'Delete/drop' to drop
database, especially just created, PostgreSQL server reports:
WARNING: could not rem
2009/8/11 hubert depesz lubaczewski :
> While testing deferred unique constraints I found this:
>
> # CREATE TABLE test (
> i INT4 PRIMARY KEY
> );
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "test_pkey"
> for table "test"
> CREATE TABLE
>
> # set constraints test_pkey defe
While testing deferred unique constraints I found this:
# CREATE TABLE test (
i INT4 PRIMARY KEY
);
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "test_pkey" for
table "test"
CREATE TABLE
# set constraints test_pkey deferred;
ERROR: constraint "test_pkey" does not exist
Th
10 matches
Mail list logo
