pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schaber <schabi@logix-tt.com>
To: andrew@supernews.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] Vacuum error on database postgres
Date: Fri, 15 Sep 2006 14:44:28 +0200
Message-ID: <450AA02C.60000@logix-tt.com> (raw)
In-Reply-To: <slrnegl7oq.2ea3.andrew+nonews@atlantis.supernews.net>
References: <44F82150.5000809@pnlassociates.com>
	<4001.1157121669@sss.pgh.pa.us>
	<ee7pua$2bou$1@news.hub.org>
	<27602.1158238299@sss.pgh.pa.us>
	<45095CDD.8090704@squeakycode.net>
	<29469.1158247230@sss.pgh.pa.us>
	<45097CF4.7040409@commandprompt.com>
	<3024.1158266129@sss.pgh.pa.us>
	<450A815C.6000709@logix-tt.com>
	<slrnegl7oq.2ea3.andrew+nonews@atlantis.supernews.net>

Hi, Andrew,

Andrew - Supernews wrote:

>> Is there any reason to allow ANALYZE run insinde a transaction at all?
> 
> Absolutely. In a large transaction that radically changes the content of
> the database, it is often necessary to analyze in order to avoid getting
> extremely bad query plans for later commands in the transaction.

OK, I see.

But this leads to the danger that, should the transaction abort
afterwards, we're left with borked stats, or are those rolled back
accordingly?

Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org

Attachments:

  signature.asc (application/pgp-signature, 251B) download

view thread (21+ messages)  latest in thread

Message-ID: <450AA02C.60000@logix-tt.com>
Permalink:  ../450AA02C.60000@logix-tt.com/
Also on:    postgresql.org/message-id/450AA02C.60000@logix-tt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: schabi@logix-tt.com, andrew@supernews.com, pgsql-hackers@postgresql.org
  Subject: Re: [ADMIN] Vacuum error on database postgres
  In-Reply-To: <450AA02C.60000@logix-tt.com>
  References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> <ee7pua$2bou$1@news.hub.org> <27602.1158238299@sss.pgh.pa.us> <45095CDD.8090704@squeakycode.net> <29469.1158247230@sss.pgh.pa.us> <45097CF4.7040409@commandprompt.com> <3024.1158266129@sss.pgh.pa.us> <450A815C.6000709@logix-tt.com> <slrnegl7oq.2ea3.andrew+nonews@atlantis.supernews.net> <450AA02C.60000@logix-tt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox