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
Hi,
On Mon, 30 Oct 2000, Thomas Lockhart wrote:
> > Just to let you know it looks like ver 7.0 does not run on SuSE7.0 SMP
> > Kernel. Has this been fixed on 7.02 at all?
>
> As Peter asked, we need more info to help you. But fwiw, I've been
> running on SMP linux for several years with no probl
Hi,
On Wed, 14 Feb 2001 [EMAIL PROTECTED] wrote:
> fmatheus ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> NOTICE: pg_setlocale()
>
> Long Description
> Im a Debian user of postgresql version 7.0.3-4.
> libc6 and loca
On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote:
> Installing Postgress on a Red Hat 7.0 Server, some regression test
> failed (see below). How can i fix this failed queries?
I had similar results here at SuSE. They came from a locale bug in
glibc-2.2 . As a workaround, try to unset LANG or set it t
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
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
Hi Bruce,
On Wed, 5 Sep 2001, Bruce Momjian wrote:
> I have a patch here that handles all the TCL/UTF issues.
> Would you let me know if it is OK?
I think, it isn't really a clean fix. It only works, if your
database's encoding and Tcl's system encoding are identical. If the
database uses a dif
Hi,
as of 7.2b5 'libpq++.h' includes 'libpq++/pgconnection.h' which in
turn tries to include 'postgres_fe.h' which can't be found because it
has bee moved to the 'internal' subdirectory.
Are applications now required to supply -I/usr/include/pgsql/internal
in addition to -I/usr/include/pgsql or
Hi,
I am not sure whether the behaviour described below is to be expected
or to be considered as a bug, but I bet you can tell me ;)
I have a table defined as follows:
CREATE TABLE "foo" (
"id" int NOT NULL,
"name" character varying(256) NOT NULL,
"street" character vary
On Wed, 27 Feb 2002 at 22:57, Tom Lane wrote:
> Also, to put the rubber to the road: if you force an indexscan by
> doing "set enable_seqscan = off", does it get faster or slower?
> (EXPLAIN ANALYZE would be useful here.)
I've just found a case where forcing indexscans results in much higher
spe
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
> >
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
Hi,
On Thu, 28 Feb 2002 at 16:10, Tom Lane wrote:
> > -> Index Scan using foo2_pkey on foo2
> > (cost=0.00..10387.79 rows=352072 width=4)
> > (actual time=0.26..174.32 rows=38432 loops=1)
>
> The actual rows read from this indexscan seem to be many fe
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...
&
Hi,
On Tue, 9 Apr 2002 at 19:43, Thomas Lockhart wrote:
> I don't think that our code checks explicitly for a "-1" return, since
> the range is checked just before the call, but it would probably be a
> good idea if it did
Indeed.
As I noticd yesterday, glibc's mktime() has in the current snap
Hi,
On Mon, 17 Jun 2002 at 20:47, David M. Kaplan wrote:
> host all 127.0.0.1 0.0.0.0identsameuser
If you want this entry to match only the loopback device, the mask has
to be 255.255.255.255 instead of 0.0.0.0. A mask of 0.0.0.0 causes
*all* IP addresses to match this
On Tue, 18 Jun 2002 at 09:28, David M. Kaplan wrote:
> Thanks, that did fix that problem. Now I have another one. The line:
>
> hostall192.168.1.2255.255.255.128password
>
> matches all ip addresses of the form 192.168.1.x. If I change the mask
> to 255.255.255.255 it no longer
On 4 Sep 2002 at 12:48, Rod Taylor wrote:
> This item:
> Add file to hold passwords using PGPASSWORDFILE environment variable
>
> Has been completed, and will be a part of the 7.3 release.
Is there a default file name like ~/.pgpassword so that this feature
can be used without setting yet anothe
On 5 Sep 2002 at 12:33, Rod Taylor wrote:
> My understanding is that it's a single password, not a list.
>
> As such you would probably not want a default, as each database you
> connect to will (should?) have a different password. By setting a
> default file we may encourage users to use the sa
On Wed, 6 Aug 2003 at 18:02, Tom Lane wrote:
> Mahlon Stacy <[EMAIL PROTECTED]> writes:
> > Newer versions of TCL implement ByteArray objects which are
> > the best fit for Postgresql Large Object functions.
>
> How newer is "newer"? That is, what compatibility problems might we
> create if we ma
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
When initially starting up, syslogger keeps stdout and stderr open
instead of closing them and reopening them from /dev/null for
proper daemonisation.
How exactly could it "close and reopen" them without losing their
ide
On Thu, 20 Sep 2012 at 10:31, Heikki Linnakangas wrote:
I believe Tom is referring to the removal of silent_mode in 9.2, see
http://archives.postgresql.org/pgsql-general/2011-06/msg00796.php
and
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02156.php.
"We removed logic associated w
On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
(I assume you mean pg_ctl not pg_init?)
Yes, sorry for the confusion.
Well, I would have no objection to changing pg_ctl so that it
redirects the postmaster's stdout/stderr when a -l switch is given
(actually, I thought it did that already...).
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 --- but Reinhard is
26 matches
Mail list logo
