| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | kent(at)cpttm(dot)org(dot)mo (Kent Tong), pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Limit on updates made in a transaction |
| Date: | 2002-07-29 12:58:52 |
| Message-ID: | 200207291358.52397.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday 27 Jul 2002 4:25 am, Kent Tong wrote:
> Hi,
>
> Is there is any limit on the number of updates made to a
> postgreSQL database in a single transaction?
No - although since the machine needs to be able to rollback the updates you
could run out of resources on the machine.
> If yes, how
> can we get around this problem? For example, we need to
> update a field of many existing rows in a table triggered
> by the addition of a new row. If anything fails in the
> update process, we'd like to undone everything (including
> the addition of the new row).
No problem - that's what the system is designed for.
- Richard Huxton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jochem van Dieten | 2002-07-29 13:40:06 | Re: Is there any such thing as PostgreSQL security on a |
| Previous Message | Wim | 2002-07-29 12:58:35 | Still problems with pg_dump ad \dt... |