| From: | "Edmar Wiggers" <edmar(at)brasmap(dot)com> |
|---|---|
| To: | <pgsql-sql(at)postgreSQL(dot)org> |
| Subject: | "too big" transactions |
| Date: | 2000-10-20 00:59:54 |
| Message-ID: | NEBBIAKDCDHFGJMLHCKIAEHJCAAA.edmar@brasmap.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
How does PostgreSQL handles a "too big" transaction?
By that I mean a transaction which, after a certain point, there will be no
way to roll back. On PgSQL, maybe that only happens when the disk fills. Is
there a configurable "size" limit for a single transaction?
In addition, what happens if the disk fills up? Postgres is able to roll
back, right?
I'm assuming you can prevent the disk from actually filling up (and crashing
the whole server) by turning on quotas for the postgres super user, so that
only pgsql would complain. Please correct me if I'm wrong.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-20 01:03:00 | Re: Now 376175 lines of code |
| Previous Message | Tom Lane | 2000-10-20 00:59:51 | Re: Proposed relaxation of CREATE RULE syntax |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig May | 2000-10-20 04:58:43 | COUNT |
| Previous Message | Tom Lane | 2000-10-19 23:49:09 | Re: Conditional query plans. |