| From: | Vivek Khera <khera(at)kcilink(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: problems with transaction blocks |
| Date: | 2004-01-08 21:54:35 |
| Message-ID: | x7n08yyulg.fsf@yertle.int.kciLink.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "RM" == Rodrigo Malara <rodrigomalara(at)yahoo(dot)com(dot)br> writes:
RM> Another way is break the transaction. Instead of consisting of many
RM> inserts, each insert is a transaction itself.
RM> Do a Begin and a Commit (or rollback) circling the insert statement.
that will destroy your performance if you do it a lot. and there's no
point in doing an explicit begin/commit since PG does that implicitly
for each statement not inside a transaction already.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2004-01-08 21:58:01 | Re: problems with transaction blocks |
| Previous Message | Tom Lane | 2004-01-08 21:53:39 | Re: 7.4, 'group by' default ordering? |