Re: [GENERAL] More Snow Leopard problems...
From: Jan Otto [as...@me.com]
Sent: Monday, September 07, 2009 9:37 AM
To: Tom Lane
Cc: Levan, Jerry; pgsql-general@postgresql.org general
Subject: Re: [GENERAL] More Snow Leopard problems...
hi jerry,
>> could not lookup DNS configuration info service: (ipc/send) invalid
>> destination port
>> LOG: could not resolve "localhost": nodename nor servname provided,
>> or not known
>> LOG: disabling statistics collector for lack of working socket
>> WARNING: autovacuum not started because of misconfiguration
>> HINT: Enable the "track_counts" option.
>> DNSServiceDiscoveryLookupServer(): {/SourceCache/mDNSResponder/
>> mDNSResponder-212.1/mDNSMacOSX/DNSServiceDiscovery.c:143}
>> bootstrap_look_up() failed: $1003
>
> I wonder whether adding or removing --with-bonjour (whichever way
> you didn't configure it) would make a difference.
try killing mDNSResponder before restarting postgres:
sudo killall mDNSResponder
hopefully apple fixes this dns-problems in 10.6.1.
regards, jan otto
Wow, everything has really gone to h*ll...
I must be cursed. Yesterday I booted the SL Distribution disk and used the Disk
Utility
to check the integrity of the disk... Disk Utility could not find any problems.
Today after I found that pg would not start due to a checksum error in the
Control File
I *tried* to reboot the system but I get a kernel trap at boot so no joy in
Mudville...
I am running a clone of the system I made friday via SuperDuper. Postgresql is
running in the clone ( all I am missing is about 15 records I inserted
Saturday).
I probably will try to restore from the clone...
It might be best to reformat and reinstall SL but I find the prospect of trying
to restore and
configure the vast amount of apps mind boggling
Sigh,
Jerry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Running Totals and other stuff....
Title: Running Totals and other stuff Humpfff...Last night I tried posting this and found that dynamic IP's are now prevented from posting to the list... Did I miss the announcement? Hi, I keep all of my financial data in Postgresql ( 7.4.2). My "Check" register records deposits, withdrawals (as amount) , date, category and other stuff. The following sorta works... SELECT oid, *, (SELECT sum(amount) FROM checks WHERE x.thedate >= thedate ) AS total FROM checks x ORDER BY thedate,oid ; The problem is that all transactions on the same date get the total of all transactions for that date, so the resulting table is only "sorta" a running total. If I change the rascal to look like SELECT oid, *, (SELECT sum(amount) FROM checks WHERE x.oid >= oid ) AS total FROM checks x ORDER BY thedate,oid ; I get the right results, but this relies on the fact the oids in the check table are currently *sorted* (when the table is sorted by thedate) at least it appears that way via a very brief inspection I suspect if I deleted a record and added a record the oids would get out of sequence. Is there a slick way to tell if a column (say the oids column) is in "sorted" order when the table is sorted by date? Assuming the oids get out of wack with respect to the date, is it possible to easily construct a table of the checks sorted by date and then "glue on" a column of ascending integers so the running total sql statement will function properly? Jerry
