Hi!
Tom Lane [2005-06-02 11:46 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > I found out that activating
>
> > log_parser_stats = true
> > log_planner_stats = true
> > log_executor_stats = true
> > log_statement_stats = true
>
> > in postgresql.conf leads to this bug
>
> This is another
In message <[EMAIL PROTECTED]>, Tom Lane writes:
[EMAIL PROTECTED] writes:
> We saw the problem with async_notify again (See thread with subject
> "Postgres 7.4.6 hang in async_notify" in first message to this list
> dated "Mon, 25 Apr 2005 15:42:35 -0400") in a production setting
[EMAIL PROTECTED] writes:
> We saw the problem with async_notify again (See thread with subject
> "Postgres 7.4.6 hang in async_notify" in first message to this list
> dated "Mon, 25 Apr 2005 15:42:35 -0400") in a production setting.
I've applied a patch that (I think) will fix this. Attached is
[EMAIL PROTECTED] writes:
> We saw the problem with async_notify again (See thread with subject
> "Postgres 7.4.6 hang in async_notify" in first message to this list
> dated "Mon, 25 Apr 2005 15:42:35 -0400") in a production setting.
> Since our last instance, we converted to compiling postgres wit
We saw the problem with async_notify again (See thread with subject
"Postgres 7.4.6 hang in async_notify" in first message to this list
dated "Mon, 25 Apr 2005 15:42:35 -0400") in a production setting.
Since our last instance, we converted to compiling postgres with
debugging, so we have a stack t
Martin Pitt <[EMAIL PROTECTED]> writes:
> I found out that activating
> log_parser_stats = true
> log_planner_stats = true
> log_executor_stats = true
> log_statement_stats = true
> in postgresql.conf leads to this bug
This is another manifestation of the 7.4 problem with trying to test
superuse
This does not belong on the pgsql-bugs list. The pgsql-novice or
pgsql-performance lists seem more appropiate. I have set followups
to the pgsql-novice list.
On Thu, Jun 02, 2005 at 12:05:00 +0100,
Bahadur Singh <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I found situtation that, when I am selec
The following bug has been logged online:
Bug reference: 1697
Logged by: Bahadur Singh
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000 server
Description:Select getting slower on continously updating data
Details:
Hello,
I fo
Hi PostgreSQL developers!
We just experienced a bug that gave us a serious headache until we
found the reason. When doing "psql template1" we got an error message
psql: FATAL: invalid cache id: 30
Evert Meulie found a similar problem at
http://archives.postgresql.org/pgsql-novice/2004-11/m
