status on pgiomonitor
I'm re-writing documentation I have used in the past to give PG courses,
and at this moment I upgrading the information in my docs to fit PG 8.3.
What I'm stuck with now is pgiomonitor, which seems to not work due to
the changes that happened between 8.1 (last time I used it) and 8.3.
Does anybody know if development is still going to be done, at least to
make it fit new versions of PostgreSQL?
thanks.
Martin Marques escribió:
I'm re-writing documentation I have used in the past to give PG courses,
and at this moment I upgrading the information in my docs to fit PG 8.3.What I'm stuck with now is pgiomonitor, which seems to not work due to
the changes that happened between 8.1 (last time I used it) and 8.3.Does anybody know if development is still going to be done, at least to
make it fit new versions of PostgreSQL?
If anybody is interested (I'm not a Perl expert), I changed the line
where is asks if stats_block_level is on, to track_counts.
Now it works for PG 8.3.
I get this strange error
Caused by: org.postgresql.util.PSQLException: ERROR: could not open
relation 1663/53544/58374: No such file or directory
How do I recover from it ? Postgresql version 8.2 on windows.
I think I had an hardware issue in the past where my box rebooted few
times I assume this is due to that thing.
I tried to re index them but is not working. Any ideas ?
Can one tell how do I start the server in stand alone mode in windows ? I tried via the postgres command but still can't reindex all...
Thanks
On Apr 26, 2008, at 8:40 AM, Martin Marques wrote:
Martin Marques escribió:
I'm re-writing documentation I have used in the past to give PG
courses, and at this moment I upgrading the information in my docs
to fit PG 8.3.
What I'm stuck with now is pgiomonitor, which seems to not work due
to the changes that happened between 8.1 (last time I used it) and
8.3.
Does anybody know if development is still going to be done, at
least to make it fit new versions of PostgreSQL?If anybody is interested (I'm not a Perl expert), I changed the line
where is asks if stats_block_level is on, to track_counts.Now it works for PG 8.3.
hey neat. I wrote that years ago and its been quite dusty.
It worked then so I had nothing else to add to it.
I haven't migrated to 8.3 yet so I didn't know it broke.
Can you send me a diff?
--
Jeff Trout <jeff@jefftrout.com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
Jeff escribi�:
On Apr 26, 2008, at 8:40 AM, Martin Marques wrote:
Martin Marques escribi�:
I'm re-writing documentation I have used in the past to give PG
courses, and at this moment I upgrading the information in my docs to
fit PG 8.3.
What I'm stuck with now is pgiomonitor, which seems to not work due
to the changes that happened between 8.1 (last time I used it) and 8.3.
Does anybody know if development is still going to be done, at least
to make it fit new versions of PostgreSQL?If anybody is interested (I'm not a Perl expert), I changed the line
where is asks if stats_block_level is on, to track_counts.Now it works for PG 8.3.
hey neat. I wrote that years ago and its been quite dusty.
It worked then so I had nothing else to add to it.
I haven't migrated to 8.3 yet so I didn't know it broke.Can you send me a diff?
--- pgiomonitor 2005-04-07 13:10:23.000000000 -0300
+++ pgiomonitor-8.3 2008-04-26 09:38:11.000000000 -0300
@@ -124,7 +124,7 @@
$dbname =~ s/ [[:ascii:]]+//;
# Check to see if we have block stats enabled
-$blockOn = @{$db->selectcol_arrayref("show stats_block_level")}->[0];
+$blockOn = @{$db->selectcol_arrayref("show track_counts")}->[0];
if($blockOn ne "on")
{
print "ERROR: you need to enable stats_block_level in
postgresql.conf\n";
Mircea Moisei wrote:
I get this strange error
Caused by: org.postgresql.util.PSQLException: ERROR: could not open
relation 1663/53544/58374: No such file or directoryHow do I recover from it ? Postgresql version 8.2 on windows.
Which update? 8.2.? - newer updates may have fixed the issue.
XP or Vista?
I think I had an hardware issue in the past where my box rebooted few
times I assume this is due to that thing.
My guess is it's a good bet.
Have you fixed the problem (hardware or virus)?
I tried to re index them but is not working. Any ideas ?
So postgresql is starting but you get this error when you run a query
that should use an index?
Or do you get this when you run reindex?
Have you tried drop index then create index instead?
Is there more you know that would indicate the problem is an index?
Can one tell how do I start the server in stand alone mode in windows ?
I tried via the postgres command but still can't reindex all...
Is the postgres service running? If so you need to stop it before trying
the command line. In XP right click My Computer select manage then
services. Locate postgres and stop it.
I haven't tried on windows but as far as I know you have the same options.
From a dos prompt (I would cd to c:\program files\postgresql\8.2\bin)
enter postgres --single dbwithproblems
--
Shane Ambler
pgSQL (at) Sheeky (dot) Biz
Get Sheeky @ http://Sheeky.Biz