I don't see this as applied yet.
---
Tom Lane wrote:
> "Pelle Johansson" <[EMAIL PROTECTED]> writes:
> > The age() function seem to work by first counting months until less than a
> > month remains to to the second argument,
Sorry, I see there was later discussion.
---
Tom Lane wrote:
> "Pelle Johansson" <[EMAIL PROTECTED]> writes:
> > The age() function seem to work by first counting months until less than a
> > month remains to to the second a
"David Sanchez i Gregori" <[EMAIL PROTECTED]> writes:
> select * from(
> select min("ID") as nid from "Seguretat"."Usuarios" as j
> where not exists
> ( select 1 from "Seguretat"."Usuarios" as k where k."ID"=j."ID")
> ) as b
Confirmed here, as far back as 8.1. It sort of looks like the
indexes-fo
The following bug has been logged online:
Bug reference: 3459
Logged by: David Sanchez i Gregori
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.x
Operating system: Windows XP SP2, Linux x86, Linux X86-64
Description:Query Error : plan should not reference subp
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> One problem is that we might not have enough information about OS
> encodings, at least we cannot determine it using a portable method.
That's probably because there is no such thing as an "OS encoding".
At least on most platforms, there isn't any suc
"YaYo" <[EMAIL PROTECTED]> writes:
> test=# select * from t9;
> var
> -
> 3
> 5
> (2 rows)
>
> test=# update t9 set var=var+2;
> ERROR: duplicate key violates unique constraint "t9_var_key" /*we get the
> same conclusion*/
Sorry, Postgres does not support deferred unique constraints which is
The following bug has been logged online:
Bug reference: 3455
Logged by: YaYo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: OpenBSD4.1 and Windows 5.2.3790
Description:order of rows should not significant
Details:
test=# select version
hello,
it's not bug. Please look on
http://www.pgsql.cz/index.php/Automatic_execution_plan_caching_in_PL/pgSQL
Regards
Pavel Stehule
2007/7/17, Chris Bowlby <[EMAIL PROTECTED]>:
The following bug has been logged online:
Bug reference: 3450
Logged by: Chris Bowlby
Email address:
Hi.
I think that it is use restrictions nowThis is not a BUG.
Sure, but I'd like to notice that we don't pay attention about
mismatch of PG and OS encodings.
Ah, yes.. I also agree that it has a user's confusion.
In Japan, use is restricted by the reason referred to as that server
en
On Tue, 2007-17-07 at 00:51 +, Chris Bowlby wrote:
> Using a temporary table of the same name in repeated calls to a stored
> procedure are causing OID failure issues
This is a (well) known bug. The problem arises because plpgsql caches
the query plan used to access the temporary table, which
Chris Bowlby wrote:
> Using a temporary table of the same name in repeated calls to a stored
> procedure are causing OID failure issues, it can be re-created using the
> following useless example:
This is an unfortunate side-effect of caching access plans in PL/PgSQL
functions, see FAQ:
http://ww
The following bug has been logged online:
Bug reference: 3450
Logged by: Chris Bowlby
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.11
Operating system: SUSE Linux Enterprise Server 9 SP2
Description:Multiple Stored procedure calls cause issue with temp
tab
12 matches
Mail list logo
