All's quiet ... RC3 packaging ...

I just have to setup a trong logging of users postgres activity using php
script.

It's work well and my disk is going full quickly.
i have a file like this

{ TARGETENTRY
:resdom
{ RESDOM
:resno 2
:restype 1043
:restypmod 24
:resname "abrev_formation"
:reskey 0
:reskeyop 0
:resgroupref 0
:resjunk false
}

it's to hard to exploit this file to extract a user and machine from where
they work.

Some help for managing logging

Fouad Fezzi

There is an ELOG_TIMESTAMPS options and some others in include/config.h or
include/config.h.in. I think that is where you get the pid of the
backend and stuff. I agree it needs more detail, at least the process
id.

[ Charset ISO-8859-1 unsupported, converting... ]

I just have to setup a trong logging of users postgres activity using php
script.

It's work well and my disk is going full quickly.
i have a file like this

{ TARGETENTRY
:resdom
{ RESDOM
:resno 2
:restype 1043
:restypmod 24
:resname "abrev_formation"
:reskey 0
:reskeyop 0
:resgroupref 0
:resjunk false
}

it's to hard to exploit this file to extract a user and machine from where
they work.

Some help for managing logging

Fouad Fezzi

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

The Hermit Hacker <scrappy@hub.org> writes:

Everything has been quiet, as far as patches are concerned, for the past
24+hrs ... I'd like to roll (and actually announce) an solid RC3 tonight,
with announce first thing tomorrow morning, unless anyone has anythign
they aer sitting on?

I think we've got to remove that failing horology test before we wrap RC3.

regards, tom lane

On Wed, 4 Apr 2001, Tom Lane wrote:

The Hermit Hacker <scrappy@hub.org> writes:

Everything has been quiet, as far as patches are concerned, for the past
24+hrs ... I'd like to roll (and actually announce) an solid RC3 tonight,
with announce first thing tomorrow morning, unless anyone has anythign
they aer sitting on?

I think we've got to remove that failing horology test before we wrap RC3.

can we comment out the test for now, so that its still in there, but not
tested? or is there absolutely non way that we can fix that in the long
term?

The Hermit Hacker <scrappy@hub.org> writes:

On Wed, 4 Apr 2001, Tom Lane wrote:

I think we've got to remove that failing horology test before we wrap RC3.

can we comment out the test for now, so that its still in there, but not
tested? or is there absolutely non way that we can fix that in the long
term?

Commenting it out was the only idea that I had. Maybe Thomas has a
better idea, though.

regards, tom lane

Everything has been quiet, as far as patches are concerned,
for the past 24+hrs ... I'd like to roll (and actually announce)
an solid RC3 tonight, with announce first thing tomorrow morning,
unless anyone has anythign they aer sitting on?

We still have opened report about losing files after backend
crash... No new input from Konstantin -:(
I'll run some tests...

Vadim

On Wed, 4 Apr 2001, Mikheev, Vadim wrote:

Everything has been quiet, as far as patches are concerned,
for the past 24+hrs ... I'd like to roll (and actually announce)
an solid RC3 tonight, with announce first thing tomorrow morning,
unless anyone has anythign they aer sitting on?

We still have opened report about losing files after backend
crash... No new input from Konstantin -:(

if not easily recreateable, we can leave that one as somethign for v7.1.1
...

I'll run some tests...

then again, if it is easily recreatable ... :)

On Thursday 05 April 2001 00:41, Thomas Lockhart wrote:

I've got patches for the regression tests to work around the "time with
time zone" DST problem. Will apply to the tree asap, and will post a
message when that is done.

Is RC3 going out or should I think about RC2?

Saludos... ;-)

--
El mejor sistema operativo es aquel que te da de comer.
Cuida tu dieta.
-----------------------------------------------------------------
Martin Marques | mmarques@unl.edu.ar
Programador, Administrador | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------

I've got patches for the regression tests to work around the "time with
time zone" DST problem. Will apply to the tree asap, and will post a
message when that is done.

- Thomas

The Hermit Hacker <scrappy@hub.org> writes:

On Wed, 4 Apr 2001, Mikheev, Vadim wrote:
Everything has been quiet, as far as patches are concerned,
for the past 24+hrs ... I'd like to roll (and actually announce)
an solid RC3 tonight, with announce first thing tomorrow morning,
unless anyone has anythign they aer sitting on?

We still have opened report about losing files after backend
crash... No new input from Konstantin -:(

I'd suggest we go ahead and roll RC3. There's no way to tell how long
it might take to diagnose Konstantin's report, and the other issues we
had seem to be closed out at the moment.

regards, tom lane

On Wed, 4 Apr 2001, Thomas Lockhart wrote:

I've got patches for the regression tests to work around the "time with
time zone" DST problem. Will apply to the tree asap, and will post a
message when that is done.

Sounds cool ... I'll scheduale an RC3 then, around that bug being fixed
...

On Wed, Apr 04, 2001 at 10:56:27AM -0400, Tom Lane allegedly wrote:

The Hermit Hacker <scrappy@hub.org> writes:

On Wed, 4 Apr 2001, Tom Lane wrote:

I think we've got to remove that failing horology test before we wrap RC3.

can we comment out the test for now, so that its still in there, but not
tested? or is there absolutely non way that we can fix that in the long
term?

Commenting it out was the only idea that I had. Maybe Thomas has a
better idea, though.

Why not work with a maximum error in the regression tests? For instance,
allow a small difference after the 8th digit? That would pick out the
real bugs and let the round-off errors pass, right?

Mathijs
--
It's not that perl programmers are idiots, it's that the language
rewards idiotic behavior in a way that no other language or tool has
ever done.
Erik Naggum