The following bug has been logged online:
Bug reference: 2044
Logged by: balamuralikn
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: Win 2000
Description:OLEDB Driver error
Details:
iam facing the following error on execution of the giv
Dear All,
A program produces the wrong output for any given input.
Here comes bug report:
1. Database dump is attached.
2. Input: "BEGIN; INSERT INTO test1(some_text) VALUES ('test1'); SELECT
lastval() as id; END;"
3. Output:
INSERT 0 1
id
3
(1 row)
4. Exspected Output:
id
2
(1 row)
The following bug has been logged online:
Bug reference: 2046
Logged by: Chris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows
Description:defective date_trunc
Details:
Postgresql 8.0
select date_trunc('week',TO_DATE('2005-01-01',
The following bug has been logged online:
Bug reference: 2043
Logged by: Man-Chicken
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: BSD
Description:Documentation is incorrect...
Details:
http://www.postgresql.org/docs/8.0/interactive/func
Hi,
ich bin dabei DB-Server zu einem Cluster zusammen zuführen mit
PGCLUSTER. Hat schon jemand von euch damit gearbeitet und kann mir mal
seine Meinung/Erfahrung dazu sagen (positiv oder negativ).
Werde auch meine Erfahrung noch Erfolg hier mal posten.
Server: 7.4.1 (suse9.0)
pgcluster-1.1
Grüs
The following bug has been logged online:
Bug reference: 2045
Logged by: Akio Iwaasa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 , 8.1
Operating system: RedHat EL ES 3.0
Description:test_fsync "-f" option
Details:
Dear Sirs,
This is a bug report of fsy
Chris wrote:
> Postgresql 8.0
>
> select date_trunc('week',TO_DATE('2005-01-01','-mm-dd'))
Upgrade to 8.0.4. This bug is fixed there.
alvherre=# select date_trunc('week',TO_DATE('2005-01-01','-mm-dd'));
date_trunc
2004-12-27 00:00:00-03
(1 fila)
Akio Iwaasa wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2045
> Logged by: Akio Iwaasa
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0 , 8.1
> Operating system: RedHat EL ES 3.0
> Description:test_fsync "-f" option
> Details:
>
Chris wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2046
> Logged by: Chris
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows
> Description:defective date_trunc
> Details:
>
> Postgresql 8.0
>
> selec
Man-Chicken wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2043
> Logged by: Man-Chicken
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: BSD
> Description:Documentation is incorrect...
> Details:
>
> http://w
On Tue, Nov 15, 2005 at 11:39:37AM +0200, Sarunas Krisciukaitis wrote:
> Dear All,
>
> A program produces the wrong output for any given input.
> Here comes bug report:
> 1. Database dump is attached.
> 2. Input: "BEGIN; INSERT INTO test1(some_text) VALUES ('test1'); SELECT
> lastval() as id; END
On Wed, Nov 16, 2005 at 06:29:40AM +0100, Tomas Zerolo wrote:
> AFAIK, serials are not guaranteed to produce sequential values; tehy
> will produce unique values. That means that they can (and sometimes
> will) jump.
In this particular case, however, the behavior is due to the rule
on test1:
CREA
On Tue, Nov 15, 2005 at 10:51:10PM -0700, Michael Fuhr wrote:
> On Wed, Nov 16, 2005 at 06:29:40AM +0100, Tomas Zerolo wrote:
> > AFAIK, serials are not guaranteed to produce sequential values; tehy
> > will produce unique values. That means that they can (and sometimes
> > will) jump.
>
> In this
13 matches
Mail list logo