Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-10 Thread Robert Young
Anyway... Thanks to all of you for answering my puzzles, even though none of you gave feasible answer ... On Fri, Nov 11, 2011 at 00:42, Bruce Momjian wrote: > Robert Young wrote: >> The answer is simple. >> You said, just the stats collector have some trouble. >> Then I sa

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-10 Thread Robert Young
11 07:09, Robert Young wrote: >> >> 2.If the underling lack of hostname or DNS facility, Anyway, PG should >> be founctional without it. > > It is. It's just the stats collector that won't work, and autovacuum which > depends on a working stats collector. Otherwi

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-10 Thread Robert Young
whole database is almost functional, we won't fix the whole. Component of it get in trouble, we fix the component. The whole is almost functional can be a reason that we should not fix the nonfunctional component. On Thu, Nov 10, 2011 at 06:36, Heikki Linnakangas wrote: > On 10.11.2011 07:09

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-09 Thread Robert Young
ture that PG stated supported. Controversy is here! PG support TCP/IP sockets and UNIX-domain sockets. So I said: On Thu, Nov 10, 2011 at 05:09, Robert Young wrote: > Q1: Should it also be functional without sockets? > A1: If the system lack of IP sockets, PG should be founctional with > u

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-09 Thread Robert Young
mware ESX which runs on bare metal. The conclusion is obvious: If underling lack of hostname or DNS facility, PG should be founctional with IP address. Still: On Tue, Nov 1, 2011 at 08:04, Robert Young wrote: > Database should be functional without underlying hostname or DNS facility. On Thu

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-09 Thread Robert Young
Sure! It give the right information to workaround the problem. But as I said: On Fri, Oct 28, 2011 at 07:11, Robert Young wrote: > 2.hard-coding is NOT configurable, that is the problem must be aided > from OUTSIDE of the system to workaround. > And On Tue, Nov 1, 2011 at 08:04, Rob

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-09 Thread Robert Young
Sure! It give the right information to solve the problem. But as I said: On Fri, Oct 28, 2011 at 07:11, Robert Young wrote: > 2.hard-coding is NOT configurable, that is the problem must be aided > from OUTSIDE of the system to workaround. > On Wed, Nov 9, 2011 at 16:48, Bruce Momji

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-09 Thread Robert Young
system was shut down at 2011-10-27 09:43:18 GMT LOG: database system is ready to accept connections On Wed, Nov 9, 2011 at 15:06, Bruce Momjian wrote: > Andres Freund wrote: >> Hi Robert, >> >> On Thursday, October 27, 2011 12:38:02 PM Robert Young wrote: >> > Wha

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-01 Thread Robert Young
You quoted Tom Lane. But I already replied him as following, So I quote mine again: > On Fri, Oct 28, 2011 at 17:12, Robert Young wrote: >> It is client applications and services,NOT client applications and database. >> It just term's (client applications, services) misleadi

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-11-01 Thread Robert Young
On Fri, Oct 28, 2011 at 15:40, Robert Young wrote: > Which wrong? > 1.I got no money to buy a good machine to run both the services and database. > 2.I got no money to buy a good machine to run both the services and > client applications. > 3.Client applications hard-coding &quo

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
and services". What you said is your assumption. Without knowledge, you should consider them equivalent. PG got no priority. On Fri, Oct 28, 2011 at 16:35, Tom Lane wrote: > Robert Young writes: >> You got no knowledge about "client applications". >> What you said is

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
You got no knowledge about "client applications". What you said is your assumption. Without knowledge, you should consider them equivalent. PG got no priority. On Fri, Oct 28, 2011 at 16:03, Heikki Linnakangas wrote: > On 28.10.2011 18:40, Robert Young wrote: >> >> W

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
Which wrong? 1.I got no money to buy a good machine to run both the services and database. 2.I got no money to buy a good machine to run both the services and client applications. 3.Client applications hard-coding "localhost". 4.PG hard-coding "localhost". On Fri, Oct 28, 2

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
But...database and other services are not relevant. And...client apps of course relevant to that services,but I have to kluge to separate the increasing load. And...client apps is just as same as PG hard-coding "localhost". On Fri, Oct 28, 2011 at 15:00, Tom Lane wrote: > Alvaro Herrera writes:

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
Don't be so surprised, because the app just as same as PG hard-coding "localhost". On Fri, Oct 28, 2011 at 14:54, Alvaro Herrera wrote: > > Excerpts from Robert Young's message of vie oct 28 11:47:14 -0300 2011: >> >> I just migrate some services from one machine to another but database >> stay t

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
I just migrate some services from one machine to another but database stay there. So, I think the most simple solution is to change “localhost” point to the new one, so that I need no modification of client applications. But found PG gave warnings. On Fri, Oct 28, 2011 at 13:39, Alvaro Herrera wr

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-28 Thread Robert Young
I am just wondering, why "localhost" entry in /etc/hosts is editable and why 127.0.0.1 not fixed with loopback interface? should you agree with that we should submit a patch to kernel to resolve "localhost" to 127.0.0.1 statically need no entry in /etc/hosts and loopback interface bind to 127.0.0.1

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-27 Thread Robert Young
including hard-coding 1 minute as 60 seconds. On Thu, Oct 27, 2011 at 13:13, Heikki Linnakangas wrote: > On 27.10.2011 15:57, Robert Young wrote: >> >> But,I think insistence of hard-coding should be even worse than broken >> configuration. >> And hard-coding should nev

Re: [BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-27 Thread Robert Young
But,I think insistence of hard-coding should be even worse than broken configuration. And hard-coding should never be a good work ethics of a professional programmer. On Thu, Oct 27, 2011 at 12:12, Andres Freund wrote: > Hi Robert, > > On Thursday, October 27, 2011 12:38:02 PM Robert Yo

[BUGS] Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

2011-10-27 Thread Robert Young
What Would Happen if I got NO "localhost" entry in my /etc/hosts ? statistics and autovacuum would be disabled: # /usr/local/pgsql/bin/postgres -i -p 15432 -D data LOG: could not resolve "localhost": no address associated with name LOG: disabling statistics collector for lack of working socket W

Re: [BUGS] incompatible pointer type

2011-10-19 Thread Robert Young
al; On 2011-10-19, Robert Young wrote: > Perfect! > I've update my m4 to version 1.4.13 > from: > http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz > the problem solved perfectly! > Thank You !!! > > # /usr/bin/gm4 --version > m4 (GNU M4) 1.4.13 >

Re: [BUGS] incompatible pointer type

2011-10-18 Thread Robert Young
It is hard to figure out,but I inspect the source code,told me: http://ftp.openbsd.org/pub/OpenBSD/4.9/sys.tar.gz:/usr.bin/m4/PSD.doc/m4.ms: Line35: m4.ms 6.3 (Berkeley) 6/5/93 On Wed, Oct 19, 2011 at 05:12, Tom Lane wrote: > Robert Young writes: >> I've update my m4 to version

Re: [BUGS] incompatible pointer type

2011-10-18 Thread Robert Young
So,I think it'd better to check the m4 compatiblity in ./configure On Wed, Oct 19, 2011 at 05:10, Robert Young wrote: > Perfect! > I've update my m4 to version 1.4.13 > from: > http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz > the problem solv

Re: [BUGS] incompatible pointer type

2011-10-18 Thread Robert Young
Perfect! I've update my m4 to version 1.4.13 from: http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz the problem solved perfectly! Thank You !!! # /usr/bin/gm4 --version m4 (GNU M4) 1.4.13 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or late

Re: [BUGS] incompatible pointer type

2011-10-18 Thread Robert Young
.. 454 PLpgSQL_case_when *casewhen; 455 } 456 /* Line 193 of yacc.c. */ 457 #line 458 "pl_gram.c" 458 YYSTYPE; and cause the generated pl_gram.c problematic. On Tue, Oct 18, 2011 at 18:22, Tom Lane wrote: > Robert Young writes: >&

[BUGS] incompatible pointer type

2011-10-18 Thread Robert Young
Platform: OpenBSD 4.9 GENERIC.MP#819 amd64 Intel(R) Xeon(R) CPU E5620 @ 2.40GHz Error: gmake[4]: Entering directory `/tmp/pgxc/git/src/pl/plpgsql/src' /usr/bin/bison -d -o pl_gram.c gram.y gcc -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wformat