Andrew Dunstan wrote:
Tom Lane wrote:
Somebody just yesterday stuck an
fprintf(stderr,...); exit(1) into one of the pgport routines. This
sucks, but there is not a lot else that can be done if the code needs
to exist in both backend and clients. It'd be better to propagate the
error
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Somebody just yesterday stuck an
fprintf(stderr,...); exit(1) into one of the pgport routines. This
sucks, but there is not a lot else that can be done if the code needs
to exist in both backend and clients. It'd
Peter Eisentraut wrote:
Am Montag, 18. Oktober 2004 19:43 schrieb Tom Lane:
An alternative possibility is to stop pretending that pgport is agnostic
about whether it is in backend or frontend. This might mean some
duplication of code between src/port/ and src/backend/port/, but if
that's
Am Montag, 18. Oktober 2004 19:43 schrieb Tom Lane:
An alternative possibility is to stop pretending that pgport is agnostic
about whether it is in backend or frontend. This might mean some
duplication of code between src/port/ and src/backend/port/, but if
that's what it takes to have sane
As has previously been pointed out, the strings marked up for gettext
translation in the pgport library don't work and need to be moved back
to where they once came from, unless someone wants to add gettext and
locale setup in pgport. (That might be silly, because in theory locale
and gettext
Peter Eisentraut wrote:
As has previously been pointed out, the strings marked up for gettext
translation in the pgport library don't work and need to be moved back
to where they once came from, unless someone wants to add gettext and
locale setup in pgport. (That might be silly, because
Bruce Momjian [EMAIL PROTECTED] writes:
Error codes seem like a lot more work than it is worth. I vote for
adding gettext support to /port. Also adding error codes duplicates all
the error strings in the call sites.
Added to open items list:
* Add gettext support to src/port
He who
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Error codes seem like a lot more work than it is worth. I vote for
adding gettext support to /port. Also adding error codes duplicates all
the error strings in the call sites.
Added to open items list:
* Add gettext
Tom Lane wrote:
Somebody just yesterday stuck an
fprintf(stderr,...); exit(1) into one of the pgport routines. This
sucks, but there is not a lot else that can be done if the code needs
to exist in both backend and clients. It'd be better to propagate the
error condition back to the caller.
An
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Somebody just yesterday stuck an
fprintf(stderr,...); exit(1) into one of the pgport routines. This
sucks, but there is not a lot else that can be done if the code needs
to exist in both backend and clients. It'd be better to
10 matches
Mail list logo
