[EMAIL PROTECTED] writes:
> gcc2.95; hppa2.0-hp-hpux10.20, postgresql 7.1.2
> make check checks the first group all right (tests check out ok and
> a process "postgres:" shows up in the process list.
> When "make check" displays "parallel group (18 tests): point lseg"
> the "postgres:" process di
[EMAIL PROTECTED] writes:
> As far as I know, the postmaster terminated correctly, but now
> when I restart it I have:
> DEBUG: database system was shut down at 2001-07-30 21:17:17 BST
> DEBUG: CheckPoint record at (0, 214140268)
> DEBUG: Redo record at (0, 214140268); Undo record at (0, 0);
On 30-Jul-2001 Tom Lane wrote:
>> DEBUG: database system was shut down at 2001-07-30 21:17:17 BST
>> DEBUG: CheckPoint record at (0, 214140268)
>> DEBUG: Redo record at (0, 214140268); Undo record at (0, 0); Shutdown
>> TRUE
>> DEBUG: NextTransactionId: 221440; NextOid: 617393
>> FATAL 2: Z
Mark J Hewitt <[EMAIL PROTECTED]> writes:
> Thanks for the humane treatment of such a mundae problem!
Well, it *is* a bug, albeit of the "misleading error message" variety
rather than anything more critical. If you are interested in applying
a source patch to fix that problem, see
http://www.ca
[EMAIL PROTECTED] writes:
> [ SELECT DISTINCT ON in a subquery-in-FROM misbehaves ]
Oooh, good catch! I had thought about pushing down quals into a SELECT
DISTINCT, and concluded it was OK because the qual would eliminate all
or none of a set of not-DISTINCT rows. But I forgot about DISTINCT ON
Anthony Wood ([EMAIL PROTECTED]) reports a bug with a severity
of 1
The lower the number the more severe it is.
Short Description
subquery results bypassed
Long Description
The second query in the example code should return:
a | b | c
---+---+---
(0 rows)
but actually returns
a | b | c
-
mark hewitt ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Postmaster will not restart
Long Description
Afetr several very happy years of using PostgreSQL, I finally
have a serious problem.
As far as I know, the postmaster ter
Volker Hetzer ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
pg_regress fails at "point" test
Long Description
gcc2.95; hppa2.0-hp-hpux10.20, postgresql 7.1.2
make check checks the first group all right (tests check out ok and
