pgsql-bugs is much more appropriate, especially for problem reports
against a beta version.
I will keep this in mind in the outside chance that I run into another
issue :)
I tried to reproduce this without any success. Given the inconsistency
of the behavior, I'm wondering about hardware fla
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] ("Sharon Schooley") would
write:
> We are looking for a 24/7 PostgreSQL solution. I've read some
> postings and information on various solutions including Taygeta,
> pgpool, and Mammoth PostgreSQL with Heartbeat. If there are any
> users o
Hi,
I am trying to recover database. Earlier postmaster
was not starting saying invalid primary and secondary
checkpoints and a file in pg_xlog was not found.
So I used pg_resetxlog. This made postmaster start.
But I am not seeing most of the data and many tables.
I then tried using pgfsck on my
Michael Long <[EMAIL PROTECTED]> writes:
> If this is not the correct place report this type thing please let me
> know and I will post it to the correct location.
pgsql-bugs is much more appropriate, especially for problem reports
against a beta version.
> I was able to successfully alter a col
Hi Everybody,
If i do vacuumdb -z daily as a part of my
maintanence, do i have to still vacuum analyze each table in the
database ?. The reason i am asking is that even though i do vacuumdb
daily my stats are not updated properly in pg_class view and the
reltuples values is much higher than
Hello,
We are looking for a 24/7 PostgreSQL solution. I've read some postings and
information on various solutions including Taygeta, pgpool, and Mammoth
PostgreSQL with Heartbeat. If there are any users of these or other
PostgreSQL high availability solutions out there, can you respond a
I have moved the MinGW/Win32 project page into FAQ_MINGW in CVS. I
updated it to be more of an FAQ than a project page, and moved the TODO
items the proper places in our official project.
---
Robert Treat wrote:
> On Tuesda
I have renamed FAQ_MSWIN to FAQ_CYGWIN.
---
Robert Treat wrote:
> On Tuesday 21 September 2004 04:35, Magnus Hagander wrote:
> > > > When starting the Windows psql client I get a warning that the
> > > > "console codepage (4
Sounds like the Oracle parameter TIMED_STATISTICS. Costs you soo little
in performance, but saves you a pile in troubleshooting. Many DBA's
still set it to false to "save the expense". Nice to know the same
exists here.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-Original Messa
On Fri, Oct 08, 2004 at 10:46:56AM -0400, Doug Y wrote:
> Michael Fuhr wrote:
> >
> >Does postgresql.conf have stats_command_string = true?
> >
> Thanks, setting that did the trick whats the performance hit for
> having it enabled?
I haven't done any tests to determine the performance penalt
Michael Fuhr wrote:
On Fri, Oct 08, 2004 at 09:54:08AM -0400, Doug Y wrote:
SELECT * FROM pg_catalog.pg_stat_activity;
The current_query and query_start columns are always empty. Obviously
this makes it hard to monitor problems with the various admin tools, etc.
Does postgresql.conf have s
On Fri, Oct 08, 2004 at 09:54:08AM -0400, Doug Y wrote:
>
> SELECT * FROM pg_catalog.pg_stat_activity;
>
> The current_query and query_start columns are always empty. Obviously
> this makes it hard to monitor problems with the various admin tools, etc.
Does postgresql.conf have stats_command_st
Hello,
When I do the following:
SELECT * FROM pg_catalog.pg_stat_activity;
The current_query and query_start columns are always empty. Obviously
this makes it hard to monitor problems with the various admin tools, etc.
I'm guessing there's a setting or something that needs updated, I just
need a
13 matches
Mail list logo
