Larry Rosenman [EMAIL PROTECTED] writes:
Reply from SCO:
Indeed. For inf, infinity, and nan, but not
nan(digits), the pointer is left at the trailing
matched character instead of the next.
Moreover, checking our source history, it has been
broken this way for nearly 12 years. Couldn't
--On Friday, May 14, 2004 09:41:58 -0400 Tom Lane [EMAIL PROTECTED] wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
Reply from SCO:
Indeed. For inf, infinity, and nan, but not
nan(digits), the pointer is left at the trailing
matched character instead of the next.
Moreover, checking our
Please find attached a patch to integrate rotatelogs into pg_ctl. I've
noticed a couple of questions about how to do this and it seems easier
(and more elegant) to solve it in code rather than in documentation. The
patch is pretty simple and I've made it reasonably self documenting. It
test
The following patch removes an extraneous then from src/template/unixware:
Index: unixware
===
RCS file: /projects/cvsroot/pgsql-server/src/template/unixware,v
retrieving revision 1.36
diff -u -r1.36 unixware
--- unixware13 May
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Eisentraut wrote:
| Am Freitag, 14. Mai 2004 17:35 schrieb Andrew Hammond:
|
|Please find attached a patch to integrate rotatelogs into pg_ctl. I've
|noticed a couple of questions about how to do this and it seems easier
|(and more elegant) to
On Wed, 2004-05-12 at 10:37, Peter Eisentraut wrote:
In addition to the conventions that you were already told, classes starting
with Y are reserved for PostgreSQL clients.
They are? Under what circumstances would a PostgreSQL client produce an
error code?
(No such error codes exist at the
Andrew Hammond wrote:
That's essentially what the patch does. It's better because it does
it correctly instead of requiring an admin to learn how to do it
correctly.
That is entirely unconvincing handwaving. We already have a method to
do what you propose, and it's no less correct or harder
Neil Conway wrote:
On Wed, 2004-05-12 at 10:37, Peter Eisentraut wrote:
In addition to the conventions that you were already told, classes
starting with Y are reserved for PostgreSQL clients.
They are? Under what circumstances would a PostgreSQL client produce
an error code?
(No such
On Tue, 2004-05-11 at 22:56, Neil Conway wrote:
The only convention I can see is that subclass values not defined by the
SQL specification begin with 'P'. (This ought to be documented; barring
any objections, I'll commit a patch stating this in errcodes.h
explicitly).
I've applied the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Fri, May 14, 2004 at 15:31:21 -0400,
| Andrew Hammond [EMAIL PROTECTED] wrote:
|
|- - DJB's multilog requires a whole mess of configuration, and is
|difficult to run unless you're root. In which case you'd be far better
Andrew Hammond wrote:
~From what I've seen, I have to disagree. The documentation says to pipe
the stderr of the postmaster to some type of log rotation program.
which is pretty vague. It then includes an _incorrect_ example of how to
use logrotate (logrotate rotates existing log files, if you
Hackers,
Here is my current patch implementing nested transactions.
At this point I'd like some actual testing. If you have any use for
this please test it and tell me how it behaves for you. Report any
annoyances.
Still missing:
- deal with deferred triggers.
- do something with catcache
This is an updated FAQ_SCO patch that inludes yesterday's changes, and also
the float4/float8 issue I raised.
Index: FAQ_SCO
===
RCS file: /projects/cvsroot/pgsql-server/doc/FAQ_SCO,v
retrieving revision 1.9
diff -u -r1.9 FAQ_SCO
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Ouch. How long has that documentation been wrong? We have pointed
folks to that section of the docs tons of times, and no one mentioned
that logrotate is really rotatelogs, and that it is missing
parameters?
I have applied the
14 matches
Mail list logo
