pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Curious about dead rows.
Date: Wed, 14 Nov 2007 11:58:23 -0500
Message-ID: <20071114165823.GW16041@crankycanuck.ca> (raw)
In-Reply-To: <473B27FD.5050702@verizon.net>
References: <4735DBDB.5050208@verizon.net>
	<16627.1194714491@sss.pgh.pa.us>
	<4735FA9F.1080805@verizon.net>
	<b42b73150711131628q1469df3el6f557e10de07a05@mail.gmail.com>
	<473A5CC0.3060003@verizon.net>
	<b42b73150711131936l65b97b9ya7953383673b2710@mail.gmail.com>
	<473AE63D.7090305@verizon.net>
	<20071114152249.GA16041@crankycanuck.ca>
	<473B27FD.5050702@verizon.net>

On Wed, Nov 14, 2007 at 11:53:17AM -0500, Jean-David Beyer wrote:
> that I run only one at a time, or leaving psql running. But as I understand
> it, psql does not bother with transactions, and besides, I normally just do

No, every statement in psql is a transaction.  Even SELECT.  Every statement
under PostgreSQL runs in a transaction.  When you type "SELECT (1)", the
server implicitly adds the BEGIN; and END; around it.

> into my application so that the statistics counters will not count previous
> UPDATEs and ROLLBACKs when the main program that I intend and believe to do
> only INSERTs is running. It will make those statistics easier to read than
> having to subtract previous values to get the changes.

Yes.
 
> Well, it will not work because I must be superuser (i.e., postgres) to
> execute that, and if I am, I cannot read the input files. I will do it

You could grant superuser status to your user (or just connect as postgres
user) for the time being, while debugging this.

A

-- 
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke



view thread (41+ messages)  latest in thread

Message-ID: <20071114165823.GW16041@crankycanuck.ca>
Permalink:  ../20071114165823.GW16041@crankycanuck.ca/
Also on:    postgresql.org/message-id/20071114165823.GW16041@crankycanuck.ca

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: Curious about dead rows.
  In-Reply-To: <20071114165823.GW16041@crankycanuck.ca>

* 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