The following bug has been logged online:
Bug reference: 1631
Logged by: Marc Soleda
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: WinXP SP2
Description:pg_autovacuum fails when creating as a windows service
Details:
I'm installing pg_
hello.
I try to install postgres 8 (0.1 and 0.2) on
windows 2000 server
after choosing language I have message: "Failed to
create process: 2!"
What does it mean? What I have to do for
installing?
--
Best regards.
Sergey Boykov, system administrator of
communication centre of
The following bug has been logged online:
Bug reference: 1630
Logged by: Ariel E. Carná/Elizabeth Sosa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.8/7.4.6
Operating system: SuSE Linux
Description:Wrong conversion in to_date() function. See example.
Detail
The following bug has been logged online:
Bug reference: 1632
Logged by: Alexander Rusinov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: FreeBSD 5.4-PRERELEASE i386
Description:Several jailed PostgreSQL instances.
Details:
Only one ins
The following bug has been logged online:
Bug reference: 1633
Logged by: deepak
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: MS windows 2000 Server
Description:about transactions and row level locking
Details:
How we can know a record
The following bug has been logged online:
Bug reference: 1629
Logged by: mike g
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000
Description:subquery IN returns incorrect results
Details:
If I run this query:
SELECT distinct CA
The following bug has been logged online:
Bug reference: 1628
Logged by: Nathan Neuenschwander
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Win XP
Description:JDBC bug with regard to text column data type
Details:
I am using a CachedRow
O Alexander Rusinov έγραψε στις Apr 27, 2005 :
>
> The following bug has been logged online:
>
> Bug reference: 1632
> Logged by: Alexander Rusinov
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.7
> Operating system: FreeBSD 5.4-PRERELEASE i386
> Description:
On Tue, Apr 26, 2005 at 11:48:12PM +0100, Ariel E. Carná/Elizabeth Sosa wrote:
>
> Case PgSQL 7.3.8/SuSE Linux 8.2 (i586)
> ==
> PROD=# select to_date('2005-02-32', '-MM-DD');
> to_date
>
> 2005-03-04
> (1 row)
>
> Case PgSQL 7.4.6/SuSE Linu
"Ariel E. Carná/Elizabeth Sosa" <[EMAIL PROTECTED]> writes:
> PROD=# select to_date('2005-02-32', '-MM-DD');
> to_date
>
> 2005-03-04
> (1 row)
I'm not convinced that's a bug --- most implementations of the Unix
mktime function will handle out-of-range day numbers like that.
Michael Fuhr <[EMAIL PROTECTED]> writes:
> If anything I'd expect 2005-02-32 to be rejected as invalid, but I
> don't know the history or rationale behind to_date's behavior.
It is rejected by the standard date input converter:
regression=# select '2005-02-32'::date;
ERROR: date/time field value
Even _javascript_ handles those dates the same way...
On 4/27/05, Tom Lane <[EMAIL PROTECTED]> wrote:
"Ariel E. Carná/Elizabeth Sosa" <[EMAIL PROTECTED]> writes:
> PROD=# select to_date('2005-02-32', '-MM-DD');> to_date> > 2005-03-04> (1 row)I'm not convinced that's a bug --- m
"mike g" <[EMAIL PROTECTED]> writes:
> Description:subquery IN returns incorrect results
It's impossible to investigate this with the amount of information you
have provided. Please show a *self contained* example, including any
table declarations and test data needed.
On Wed, 27 Apr 2005 06:23 am, mike g wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1629
> Logged by: mike g
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows 2000
> Description: subquery IN returns incorre
>
> However we consider that to_date() exists to be
> Oracle compatible,
> and so I would regard this as a bug if and only if
> Oracle does
> something different with the same input. Anyone
> know?
>
Here is the output I get from Oracle:
=
Co
Hello, pgsql-bugs.
Here's smaller example of presentation bugs 1614 and 1616.
Run on PostgreSQL 8.0.1/8.0.2 on Windows and PostgreSQL 8.0.1 on Slackware 10.0
(throw PGAdmin3)
/*
contrib/btree_gist installed
*/
/*tool function for drop table*/
create or replace function drop_try_gist() returns vo
The following bug has been logged online:
Bug reference: 1634
Logged by: Don Courtney
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0/8.1
Operating system: Solaris 10
Description:Configure step for build does not define
HAVE_POSIX_SIGNALS
Details:
Subj: ./s
With Oracle (at least since 6.x version) this conversion is wrong.
Atentamente ,
Ariel Carná
-Mensaje original-
De: Tom Lane [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 27 de Abril de 2005 11:54 a.m.
Para: Michael Fuhr
CC: Ariel E. Carná/Elizabeth Sosa; pgsql-bugs@postgresql.
Sorry,
I used the online bug reporting form and it doesn't have an option to attach a
file to it. If it had I would have attached a pg_dump file.
Mike
On Wed, Apr 27, 2005 at 10:57:42AM -0400, Tom Lane wrote:
> "mike g" <[EMAIL PROTECTED]> writes:
> > Description:subquery IN returns in
[snip]
You are correct about the comma missing between the B and C in the query. It is
turning it into B'C. I can't think of a good way for postgres to try and
generate a warning in case a typo like this is made.
Thank you.
Mike
>
> Unless this is a copy/paste error, you have missed a , in
Don Courtney wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1634
> Logged by: Don Courtney
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0/8.1
> Operating system: Solaris 10
> Description:Configure step for build does not define
>
Nathan Neuenschwander wrote:
> I am using a CachedRowSet, the JDBC driver for PG 8.0, and j2ee.
> If the target table contains a column of data type text, the following
> causes an SQLException with a message stating that a negative value was
> returned for the column display size. If the text co
On Wed, Apr 27, 2005 at 13:56:02 +0100,
deepak <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This isn't a bug, its a question. I am moving the discussion over to
the general list.
> Bug reference: 1633
> Logged by: deepak
> Email address: [EMAIL PR
23 matches
Mail list logo
