[PERFORM] postgresql 8.0 beta - fail to collect statsistic
Hi,
I got this error message:
LOG: could not create IPv6 socket: Address family not
supported by protocol
LOG: could not bind socket for statistics collector:
Cannot assign requested address
LOG: disabling statistics collector for lack of
working socket
LOG: database system was shut down at 2004-08-24
00:07:21 EST
LOG: checkpoint record is at 0/A45360
LOG: redo record is at 0/A45360; undo record is at
0/0; shutdown TRUE
LOG: next transaction ID: 492; next OID: 17228
LOG: database system is ready
I already have a look at pgstat.c but dun know where
to fix it ( with 7.3.1 i just change the line
inet_aton("127.0.0.1", &(pgStatAddr.sin_addr));
to inet_aton("", &(pgStatAddr.sin_addr)); then
it works
this is the config of the computer:
$ uname -a
Linux grieg 2.4.26-general-64G #1 SMP Tue May 18
09:31:45 EST 2004 i686 GNU/Linux
Any help would be really appreciated.
MT
__
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [PERFORM] postgresql 8.0 beta - fail to collect statsistic
my thi ho <[EMAIL PROTECTED]> writes:
> I got this error message:
> LOG: could not create IPv6 socket: Address family not
> supported by protocol
> LOG: could not bind socket for statistics collector:
> Cannot assign requested address
> LOG: disabling statistics collector for lack of
> working socket
You have a broken networking setup, or possibly a broken DNS setup.
The machine should accept connections to 127.0.0.1 ... if it does not,
find out why not.
> I already have a look at pgstat.c but dun know where
> to fix it ( with 7.3.1 i just change the line
> inet_aton("127.0.0.1", &(pgStatAddr.sin_addr));
> to inet_aton("", &(pgStatAddr.sin_addr)); then
> it works
You were fixing the symptom and not the problem.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Re: [PERFORM] postgresql 8.0 beta - fail to collect statsistic
If IPv6 doesn't work, shouldn't it fall back to IPv4, or check IPv4 first, or something? Just wondering. -Steve Bergman ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [PERFORM] postgresql 8.0 beta - fail to collect statsistic
Steve Bergman <[EMAIL PROTECTED]> writes: > If IPv6 doesn't work, shouldn't it fall back to IPv4, It does. That was all debugged in 7.4 --- we have not seen any cases since 7.4 beta in which failures of this kind did not mean a misconfigured networking setup. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[PERFORM] How do I see what triggers are called on cascade?
I'm still having trouble with slow cascading DELETEs. What commands can I issue to see the sequence of events that occurs after I execute DELETE FROM x WHERE p; so that I can see if indexes being used correctly, or I have a constraint I don't want, etc. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PERFORM] How do I see what triggers are called on cascade?
[EMAIL PROTECTED] writes: > I'm still having trouble with slow cascading DELETEs. What commands can I issue to > see the sequence of events that occurs after I execute > DELETE FROM x WHERE p; > so that I can see if indexes being used correctly, or I have a constraint I don't > want, etc. I'd suggest starting a fresh backend, turning on log_statement, and then issuing the DELETE. log_statement will log the queries generated by the foreign-key triggers ... but only the first time through, because those triggers cache the query plans. The queries you will see will be parameterized (they'll use $1,$2,etc). You can use PREPARE and EXPLAIN ANALYZE EXECUTE to investigate what sort of plans result. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [PERFORM] postgresql performance with multimedia
--- Jan Wieck <[EMAIL PROTECTED]> wrote: > On 8/17/2004 8:44 PM, my thi ho wrote: > > > Hi, > > I am working on a project which explore postgresql > to > > store multimedia data. > > In details, i am trying to work with the buffer > > management part of postgres source code. And try > to > > improve the performance. I had search on the web > but > > could not find much usefull information. > > What version of PostgreSQL are you looking at? Note > that the buffer > cache replacement strategy was completely changed > for version 8.0, which > is currently in BETA test. A description of the > algorithm can be found > in the README file in src/backend/storage/bufmgr. oki, Thanks for the information. I have a look at 8.0 beta, but cannot start the statistic collector. (I had post this err message before for help, but havent really got any clue to fix it) > LOG: could not create IPv6 socket: Address family not > supported by protocol > LOG: could not bind socket for statistics collector: > Cannot assign requested address > LOG: disabling statistics collector for lack of > working socket btw, what i want to ask here is does postgreSQL have any kind of read-ahead buffer implemented? 'cos it would be useful in multimedia case when we always scan the large table for continous data. Thanks Ho __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
