At 23:55 2/04/01 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> While it't not a bug, it would be nice if pg_dump reproduced definitions as
>> faithfully as possible. To that end, would it be worth selecting the
>> constraints in OID order (using oid from pg_relcheck)?
>
>If
On Tue, Apr 03, 2001 at 12:59:31AM -0400, Tom Lane wrote:
> However, the horology diffs are not, and I can't reproduce them here.
> Did anyone else see that?
me too (the problem started in these days)
ciao,
andrea
---(end of broadcast)---
TIP 6: H
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 03, 2001 3:35 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [BUGS] Loosing files after backend crash
>
>
> [EMAIL PROTECTED] writes:
> > During execution of some sql code backend cra
Alessio Bragadini ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
contrib/pg_resetxlog fails to compile under Digital Unix
Long Description
Under Digital Unix (aka Compaq Tru64) 4.0f with cc, contrib/pg_resetxlog fails to
comp
Philip Warner <[EMAIL PROTECTED]> writes:
> At 00:59 3/04/01 -0400, Tom Lane wrote:
>> However, the horology diffs are not, and I can't reproduce them here.
>> Did anyone else see that?
> I've just started seeing both...
What is the date of the nearest daylight-savings transition in your
timezon
=?KOI8-R?Q?=F3=CF=CC=CF=C4=CF=D7=CE=C9=CB=CF=D7_=EB=CF=CE=D3=D4=C1?=
=?KOI8-R?Q?=CE=D4=C9=CE?= <[EMAIL PROTECTED]> writes:
>> It seems to me that your kernel must have lost that file for you; Postgres
>> wouldn't have gone out and deleted it.
> How could kernel _loose_ the file, which was already
straka ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
to_char miscalculation on April Fool's Day, the start of daylight savings
Long Description
Nip this one in the bud because knowledge of it will hinder adoption of PostgreSQ
Here is a bit more information on this date type problem.
Welcome to the POSTGRESQL interactive sql monitor:
Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 7.0.2 on i386-unknown-freebsdelf3.4, compiled by gcc 2.7.2.3]
type \? for help on slash commands
type
Patricia Holben <[EMAIL PROTECTED]> writes:
> I have loaded this new version and re-tested but don't see it fixed.
It looks fixed to me. Original SQL in constraints.sql:
CREATE TABLE INSERT_TBL (x INT DEFAULT nextval('insert_seq'),
y TEXT DEFAULT '-NULL-',
z INT DEFAULT -1 * cur
> > The RELTIME function is miscalculating dates.
> > (all my graphs were wrong today!)
Just an aside: INTERVAL is the preferred type for, uh, intervals.
RELTIME is used internally for historical reasons. In particular,
INTERVAL maintains the distinction between qualitative units such as
months a
Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> --- ./results/horology.out Mon Apr 2 17:06:59 2001
>> SELECT time with time zone '01:30' + interval '02:01' AS "03:31:00-08";
>> 03:31:00-08
>> -
>> ! 03:31:00-07
> Hmm. This is just a badly designed regression test (I can say that
Tom Lane wrote:
>
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> >> --- ./results/horology.out Mon Apr 2 17:06:59 2001
> >> SELECT time with time zone '01:30' + interval '02:01' AS "03:31:00-08";
> >> 03:31:00-08
> >> -
> >> ! 03:31:00-07
>
> > Hmm. This is just a badly desig
[EMAIL PROTECTED] writes:
> contrib/pg_resetxlog fails to compile under Digital Unix
Fixed. Thanks for the report.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgres
Patricia Holben <[EMAIL PROTECTED]> writes:
> improvement but as usual there is a related error. In the constraints=20
> test, there is a table created "INSERT_CHILD" which has a constraint and=
> then inherits from "INSERT_TBL" the constraint "insert_con" and the=20
> unnamed check. If you look
At 17:51 3/04/01 -0400, Tom Lane wrote:
>
>Rather than using "c.rcname = pg_relcheck.rcname" as part of the match
>condition, consider
> (c.rcname = pg_relcheck.rcname OR
>(c.rcname[0] = '$' AND pg_relcheck.rcname[0] = '$'))
>so that any two nameless constraints will be considered du
Philip Warner <[EMAIL PROTECTED]> writes:
> At 17:51 3/04/01 -0400, Tom Lane wrote:
>> Rather than using "c.rcname = pg_relcheck.rcname" as part of the match
>> condition, consider
>> (c.rcname = pg_relcheck.rcname OR
>> (c.rcname[0] = '$' AND pg_relcheck.rcname[0] = '$'))
>> so that any two namel
16 matches
Mail list logo
