From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Matthew Peter <survivedsushi(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: transaction toggling |
Date: | 2005-10-05 22:21:06 |
Message-ID: | 20051005222106.GH40138@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 05, 2005 at 12:49:33AM -0700, Matthew Peter wrote:
> Is there a way to disable transactions on certian
> queries? I read a while back that this wasn't
> possible, just wondering if it is in 8.1 or planned in
> the future?
>
> Does it even make a dent in the performance if a query
> is wrapped in a transaction instead of out? Such as a
> view counter, like...
>
> update views = views + 1 where x = 1;?
There was just a thread along these lines in -performance. *If*
performance becomes a concern, you can replace that update with:
insert into queue_table
Then periodically delete from that table using a plpgsql function that
can catch a row count, and use that row count to update your views
table.
But remember the first rule of performance tuning: don't.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Lawrence | 2005-10-05 22:30:53 | Trying to append text to the end of a text string |
Previous Message | Jim C. Nasby | 2005-10-05 22:17:52 | Re: Untyped result (setof / rowset) from Functions ? |