Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours. Requires jdbc
maintainers approval.
---
[EMAIL PR
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Brent Verner wrote:
> [2002-01-17 07:08] Brent
[EMAIL PROTECTED] wrote:
> Janko Richter ([EMAIL PROTECTED]) reports a bug
> with a severity of 3 The lower the number the more severe it
> is.
>
> Short Description factorial function
>
> Long Description 1. The factorial function returns 0 when the
> argument is 0. The factorial Funtion is def
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Thomas Lockhart writes:
>> This is not a bug, but the behavior required by SQL9x afaicr.
> AFAIK, this is PostgreSQL bugward compatibility. SQL says that
> current_timestamp returns the "current timestamp", which you can interpret
> any way you want
Aaron Hillegass ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
libpq needs a lo_truncate() or INV_TRUNC
Long Description
I'm using the large object interface to store documents. Sometimes the documents are
edited and get lar
Hiya! I think i've found a bug in postgres 7.2.
I have tested this on 1 box, running redhat 7.2 w/ both pg7.1.2 and pg7.2.
I've attached a dumpfile that allows you to execute this query:
INSERT INTO forum
(group_forum_id,posted_by,subject,body,date,is_followup_to,thread_id,most_recent_date)
Thomas Lockhart writes:
> > In a transaction until you commit your transaction through a jdbc
> > connection, each time you use the Current_timestamp (or 'now'), the
> > timestamps is always the same, and when your transaction is very long you
> > have undesirable effect.
>
> This is not a bug, b
> In a transaction until you commit your transaction through a jdbc
> connection, each time you use the Current_timestamp (or 'now'), the
> timestamps is always the same, and when your transaction is very long you
> have undesirable effect.
This is not a bug, but the behavior required by SQL9x af
Hello
I am using pgsql 7.1 and 7.2 and I found a bug When I use
CURRENT_TIMESTAMP in a sql query.
In a transaction until you commit your transaction through a jdbc
connection, each time you use the Current_timestamp (or 'now'), the
timestamps is always the same, and when your transaction is very
Heiko Lehmann <[EMAIL PROTECTED]> writes:
> *** ./src/include/libpq/pqsignal.h.org Mon Nov 5 18:46:33 2001
> --- ./src/include/libpq/pqsignal.h Thu Feb 21 18:51:39 2002
> ***
> *** 28,34
> #define PG_SETMASK(mask) sigprocmask(SIG_SETMASK, mask, NULL)
> #else
> ex
Good catch. I see now that AuthBlockSig is missing in
/src/include/pgsignal.h, but is referenced in pgsignal.c in both #ifdef
and #else cases.
Patch applied to 7.3 and will appear in 7.2.1.
---
Heiko Lehmann wrote:
> HAl
Peter <[EMAIL PROTECTED]> writes:
> I have the latest Cygwin and PostgreSQL 7.2. Using the installation
> instructions at http://people.freebsd.org/~kevlo/postgres/portNT.html,
> make produces the messages:
> pg_passwd.o(.text+0x763):pg_passwd.c: undefined reference to 'crypt'
If you can figure o
Olivier Garcia <[EMAIL PROTECTED]> writes:
> [ can't re-implement nextval() in plpgsql ]
The problem is that plpgsql doesn't do SetQuerySnapshot between
statements of a function, so although your different invocations are
forced to wait for each other by the LOCK statements, they cannot see
each
HAllo!
We had a problem with to compile pgsql-7.2 under SW-8.0.
In the mailing lists I found no informations.
See note for further informations.
regards Heiko
(part of 020221.postgresql-7.2)
## --
## Problem AuthBlockSig
## -
Justin Clift suggested:
http://www.ejip.net/faq/postgresql_win_setup_faq.jsp
I started from scratch following the page and adapting it where it is
out of date. I reached the stage of starting postmaster and receiving
the message:
DEBUG: pq_recvbuf: unexpected EOF on client connection
DEBUG: incomp
I have the latest Cygwin and PostgreSQL 7.2. Using the installation
instructions at http://people.freebsd.org/~kevlo/postgres/portNT.html,
make produces the messages:
pg_passwd.o(.text+0x763):pg_passwd.c: undefined reference to 'crypt'
collect2: ld returned 1 exit status
make[3]: *** [pg_passwd] E
It would be useful to be able to search a list of known bugs for
the version of postgresql that you're running. Upgrading to the
latest version to see if it sorts out a problem isn't always a
sensible option..
Andy
- Original Message -
From: "Justin" <[EMAIL PROTECTED]>
To: "Andy Marden" <
ANH TUAN ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
how to run the Postgres postmaster with -i flag
Long Description
I want to run the Postgres postmaster with -i flag.Can you show me the command?Is it
"/etc/rc.d/init.d/p
Hi!
My base contains a table objectid
create table objectid(
next bigint
);
INSERT INTO objectid values(1);
I do really need to use this table like if it was a sequence so I made
some pl/pgsql functions ( functions at the end of the mail ).
But when I run them in three psql at the same
19 matches
Mail list logo
