"Jason Palmer" <[EMAIL PROTECTED]> writes:
> ... What we experience is bizarre. We can always
> create tables with no sequences. But occasionally the database will hang
> when we attempt to create a table with a sequence or foreign key.
Yup, that's pretty bizarre. Is the backend consuming CPU
The following bug has been logged online:
Bug reference: 2710
Logged by: Jason Palmer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Redhat enterprise 4
Description:Intermittent hangs on sequence generation
Details:
We can't exactly pinpo
The following bug has been logged online:
Bug reference: 2709
Logged by: manoj
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: redhat 9
Description:how to start postgresql at startup
Details:
how to start postgresql at startup
-
Most of the relational database support that like : Oracle, DB2, MS SQL Server,
Cloudscape, Derby ... and many more.
Lachhman Dass
-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: Friday, October 20, 2006 12:32 PM
To: pgsql-bugs@postgresql.org
Cc: Lachhman Dass
The following bug has been logged online:
Bug reference: 2708
Logged by: Shutra
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5-1
Operating system: Windows or Linux
Description:Saving '\0' to bpchar by jdbc driver 8.1-407.jdbc3
Details:
Refer: http://open
"j.random.programmer" <[EMAIL PROTECTED]> writes:
> This is a regression bug between 8.1.4 and 8.1.5
> '2006-10-20 00:00:00' + interval '5' second
No, I don't think so. Every PG release back to the beginning of time
will think that is an interval + interval addition. That's one of the
system'
Hi:
This is a regression bug between 8.1.4 and 8.1.5
'2006-10-20 00:00:00' + interval '5' second
With 8.1.4, the following worked fine. However with
8.1.5, this
gives the following error.
test=# select ('2006-10-20 00:00:00' + interval '5'
second) ;
ERROR: invalid input syntax for type inter
Holger Schoenen writes:
> ERROR: invalid byte sequence for encoding "UTF8": 0xe46973
> Command was: --
[...]
> -- Started on 2006-09-15 14:56:51 Westeuropäische Normalzeit
The same problem was recently reported on the pgsql-de-allgemein list.
Would just avoiding %Z in Win32's strftime be an
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > My idea was to move relminxid to a new pg_class_nt non-transactional
> > catalog in 8.3, but we certainly need to give a solution for the problem
> > in 8.2.
>
> Didn't we pretty much shoot down the idea of a nontransactional
> exten
On Fri, Oct 20, 2006 at 09:49:47AM +0100, Heikki Linnakangas wrote:
> Alvaro Herrera wrote:
> >Tom Lane wrote:
> >>"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> >>>I just noticed that freezing a tuple (in vacuumlazy.c) is not
> >>>WAL-logged.
> >>The theory is that this doesn't matter because
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> My idea was to move relminxid to a new pg_class_nt non-transactional
> catalog in 8.3, but we certainly need to give a solution for the problem
> in 8.2.
Didn't we pretty much shoot down the idea of a nontransactional
extension catalog as being not wort
Heikki Linnakangas wrote:
> Alvaro Herrera wrote:
> >Tom Lane wrote:
> >>"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> >>>I just noticed that freezing a tuple (in vacuumlazy.c) is not
> >>>WAL-logged.
> >>The theory is that this doesn't matter because the tuple is committed
> >>either way ...
Alvaro Herrera wrote:
Tom Lane wrote:
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
I just noticed that freezing a tuple (in vacuumlazy.c) is not
WAL-logged.
The theory is that this doesn't matter because the tuple is committed
either way ... it's equivalent to a hint-bit update which we do
Lachhman Dass wrote:
> In the Update statement alias must be supported
Says who?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
14 matches
Mail list logo