[ADMIN] Re: [HACKERS] Facing authentication error on postgres 9.2 -> dblink functions
On 02/06/2013 08:09 AM, Dev Kumkar wrote:
Hello Everyone,
I am using postgres 9.2 and when executing function dblink facing a
fatal error while trying to execute dblink_connect as follows:
/SELECT * FROM dblink_connect('host=127.0.0.1 port=5432
dbname=postgres password=test')/
*ERROR*: could not establish connection DETAIL: FATAL: password
authentication failed for user "NETWORK SERVICE"
What this error is related to? Do I need to modify pg_hba.conf file by
any chance?
Thanks..
Do NOT send questions to multiple lists. That is a waste of everybody's
time. So do NOT follow up this email. This question belongs on
pgsql-general. If you have further questions pleease ask there.
The short answer is that you need to provide the user name in your
connect string.
cheers
andrew
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] [HACKERS] Postgres server goes in recovery mode repeteadly
kunal sharma wrote: Hi , We are using Postgres 8.4 and its been found going into recovery mode couple of times. The server process seems to fork another child process which is another postgres server running under same data directory and after some time it goes away while the old server is still running. There were few load issues on the server but the load didnt went above "32". We are running opensuse 10.2 x86_64 with 32Gb of physical memory. Checking the logs I found that theres a segmentation fault , Sep 26 05:39:54 pace kernel: postgres[28694]: segfault at 0030 rip 0066ba8c rsp 7fffd364da30 error 4 gdb dump shows this Reading symbols from /lib64/libdl.so.2...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libm.so.6...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 0x2ad6d7b8c2b3 in __select_nocancel () from /lib64/libc.so.6 (gdb) Please try to get a backtrace from gdb. cheers andrew -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
[ADMIN] Re: [HACKERS] pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR pg_restore: [archiver] out of memory
Amit jain wrote: Dear All, I am having a backup file in tar format. While restoring it through pg_restore instantly i am getting an following error. *Command - pg_restore -d cipa /cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR Error - pg_restore: [archiver] out of memory *I have increased shmmax , maintenace work memory but still i am getting the same error. 2. I have make all log_parameter to debug5 but still getting a single error -line while restoring not getting any log or debug info about it. Kindly help me out from this absurd behaviour of postgreSQL restoration process. Any help would be highly appreciated. Thanx in advance Please do not cross-post to multiple lists like this. (Also, adding addresses of individual hackers is not good netiquette). The -hackers list is quite inappropriate for usage questions. It looks like the problem you have is that the client is running out of memory, so changing the server's memory settings seems unlikely to have any beneficial effect. Maybe you need to look at your ulimit settings. cheers andrew -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] [HACKERS] Error"Failed to run initdb: 128!"
Pattu, Susanta Kumar wrote: Hello, I am trying to install postgresql-8.2.4 on (Remote Server) with Windows Server 2003 (pack 1). I use the postgresql-8.2.msi installer with: - national language support, PL/java, Development files selected - install a service option checked with postgres user - initialize database cluster option checked with port 5432, accept connection on all addresses not just localhost option checked, locale English UK, encoding Latin1 and super user postgres - PL/pgsql, PL/perl, PL/python selected - Adminpack selected as contrib module. I executed the installation as Administrator (user group Administrators). I got the error”* Failed to run initdb: 128! “With an error log that is empty”* Googling this error, I can see it is probably something to do with authorizations but I can't figure out what is wrong exactly. How did you fix the error? First, please do not cross-post like this. Post a query on only one list. Second, please do not post on inappropriate lists. In particular, pgsql-hackers is not for this sort of question. See also this advice: http://archives.free.net.ph/message/20070201.140142.5983e6a2.en.html cheers andrew ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] [HACKERS] grep command
Leaving aside the question of why one might want to do this, Unix 101 should show you many ways to do it. For example, sed -n -e 's/.*PG_VERSION /PG_VERSION /p' -e /PG_VERSION/q config.log Please don't cross-post questions like this, especially when it's not really a PostgreSQL question at all. cheers andrew Kuriakose, Cinu Cheriyamoozhiyil wrote: Hi All, I am giving the command cat config.log|grep -w 'PG_VERSION' Which gives the following Output: | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" | #define PG_VERSION "8.3beta2" #define PG_VERSION "8.3beta2" But the output that I would require is PG_VERSION "8.3beta2" that should occur only once, can anyone please tell me the command to get this output. Thanks in advance Regards Cinu Kuriakose ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] [HACKERS] Kill a Long Running Query
Mageshwaran wrote: Hi , Any body tell me how to kill a long running query in postgresql, is there any statement to kill a query, and also tell me how to log slow queries to a log file. First. please do not cross-post like this. Pick the correct list and use it. Second, this query definitely does not belong on the -hackers list. Third, please find a way of posting to lists that does not include a huge disclaimer and advertisements. If that is added by your company's mail server, you should look at using some other method of posting such as gmail. Fourth, please read our excellent documentation. It contains the answers to your questions, I believe. cheers andrew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] [ADMIN] SRPM for 8.0.0 beta?
Joe Conway wrote: Tom Lane wrote: Well, *Marc* is working on including less stuff; the rest of us don't necessarily agree. In particular I've got to re-incorporate any major pieces that get removed from the core distribution, since people expect to find those in the RPM set. (In principle I suppose they could be handled as independent packages with independent specfiles, but so far the path of least resistance has been to keep 'em bundled together.) On that, note that I specifically removed jdbc and tcl options from the spec file because the 8.0.0 release notes said they were removed from the distribution. I suppose at lease jdbc should be put back? It didn't seem right to include the 7.4 jdbc jars in the 8.0 source rpm, and I wasn't sure where to get the equivalent of 8.0.0beta1 jdbc jar files (if such a thing even exists). ISTM we need an S/RPM project on pgfoundry, just like the Windows installer project. (and maybe a .deb and a Solaris .pkg project too). cheers andrew ---(end of broadcast)--- TIP 8: explain analyze is your friend
