On Fri, 21 Sep 2012 at 14:17, Tom Lane wrote:
All of the use-cases I've thought of for wanting to capture stderr
output for it amount to debugging of some form or other, so it's
probably good enough for that to only work in the first logger
incarnation after database start --- bu
per-centric), I think the default should
be to let the logger do the redirection and having a command line
switch or postgresql.conf variable to suppress it for debugging
purposes.
cu
Reinhard
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes t
be closed if it is either 1
or 2, which is quite likely to happen as we've just closed these two
and open() typically gets the lowest unused FD number.
BTW, I think the other dup2() for stderr in syslogger.c should get
such a check as well, even if the clash is less likely to happen
errors it might run into before its own logging has been set up.
cu
Reinhard
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged on the website:
Bug reference: 7559
Logged by: Reinhard Max
Email address: reinh...@m4x.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
When initially starting up, syslogger keeps stdout and stderr open instead
The following bug has been logged online:
Bug reference: 4179
Logged by: Reinhard Zitzmann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Centos 5
Description:pg_standby reports "file size greater than expected"
Details:
When
lity problems might we
> create if we make this change?
ByteArrays were introduced in Tcl 8.1 (March 1999) along with the
change to use UTF-8 as internal string encoding.
cu
Reinhard
---(end of broadcast)---
TIP 9: the planner will ignor
ll need to have the password file on another than the
default place, e.g. because the home directory is on NFS and thus
considered unsafe, the file format could simply allow some sort of
include command.
cu
Reinhard
---(end of broadcast)
setting yet another environment variable?
cu
Reinhard
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
entry is being used.
If now the mask in the first entry is 0.0.0.0, any IP adress matches:
(127.0.0.1 & 0.0.0.0) == (192.168.1.1 & 0.0.0.0)
0.0.0.0 == 0.0.0.0
... and therefore the second entry is never being checked.
cu
Reinhard
---(end
tch this line.
cu
Reinhard
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
, and show a difference of 8
hour (regression.diffs attached).
I've added code to DetermineLocalTimeZone that elogs and ERROR if
mktime returns < 0, which showed, that this also happens in some other
tests, but without affecting the results there (maybe pure luck?).
cu
Reinhar
Hi,
On Fri, 1 Mar 2002 at 09:37, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
>
> > I'll tell my colleague (it's his test database, after all) that he
> > should take more realistic test data before complaining about bad
> > performance...
&
| 1010 | 1004 | 38431
foo | 1010 | 10423442 | 352072
(2 rows)
I'll tell my colleague (it's his test database, after all) that he
should take more realistic test data before complaining about bad
performance...
cu
Reinhard
---(end
On Thu, 28 Feb 2002 at 10:15, Tom Lane wrote:
> Okay. It looks like foo.id has a pretty strong but not perfect
> descending order (the correlation statistic is -0.563276). The
> planner is evidently not rating that effect strongly enough.
Yes, that seems to be the reason. When I try
S
On Thu, 28 Feb 2002 at 09:51, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > I've just found a case where forcing indexscans results in much higher
> > speed.
>
> > -> Index Scan using foo_pkey on foo
> >
I've reproduced that several times. Even on a newly started postmaster
the query takes less than 2.5 seconds with seqscans swited off.
cu
Reinhard
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
chance to avoid the
massive performance hit other than dropping the indexes before the
update and re-creating them afterwards?
The machine is a PIII/1GHz with 256MB of RAM and a UDMA100 disk
running PostgreSQL 7.2 on Linux 2.4.17.
Thanks in advance and greetings from Nuremberg,
Reinhard
ternal
in addition to -I/usr/include/pgsql or is the relocation of headers to
the 'internal' subdirectory still incomplete?
cu
Reinhard
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriat
and PL/Tcl with Tcl versions prior and after Tcl's move to UTF-8.
One Question remains here: Do --enable-multibyte and
--enable-unicode-conversion have any downsides (besides a larger
executable), if they are compiled in, but not used?
cu
Reinhard
---(end of broad
On Fri, 20 Jul 2001, Peter Eisentraut wrote:
> Reinhard Max writes:
>
> > OK, I'll pack the new stuff inside #ifdef TCL_UTF8 and define that if
> > the Tcl version is 8.1 or greater.
>
> No, please add a configure check for Tcl_UtfToExternalDString or
> some other
On Wed, 18 Jul 2001, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > On Wed, 18 Jul 2001, Bruce Momjian wrote:
> >> Do you have any idea how this will work with earlier TCL versions?
>
> > It won't. If pgtcl is supposed to still be able to
On Wed, 18 Jul 2001, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > On Wed, 18 Jul 2001, Bruce Momjian wrote:
> >> Do you have any idea how this will work with earlier TCL versions?
>
> > It won't. If pgtcl is supposed to still be able to
ng added to TCL?
According to Tcl's changelog files, it was added in 1997 for Tcl 8.1
wich was released in 1999.
cu
Reinhard Max
Maintainer of the Tcl/Tk and PostgreSQL packages for SuSE Linux
---(end of broadcast)---
TIP 3: if posting
set it to POSIX
before starting the postmaster. AFAIK glibc-2.2.2 will fix this bug.
cu
Reinhard
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
current glibc which will be fixed in the next
version.
As a workarround you can try to unset LANG and all LC_* variables.
cu
Reinhard
mbination, please let me know.
cu
Reinhard
--
If you put garbage in a computer nothing comes out but garbage.
But this garbage, having passed through a very expensive machine,
is somehow enobled and none dare criticize it.
src/backend/libpq/pqcomm.c as workarround for the PostgreSQL RPMs for
SuSE Linux which I am currently working on. The patch (hack) doing
this is also included.
Regards,
Reinhard Max
--
If you put garbage in a computer nothing comes out but garbage.
But this garbage, having passed throug
28 matches
Mail list logo
