| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: doc patch for savepoints |
| Date: | 2006-11-27 22:48:47 |
| Message-ID: | 25222.1164667727@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> + <para>
> + Savepoints use shared memory. If you use many savepoints without
> releasing them, you
> + will run out of shared memory and you may see an error like this in
> your log:
I do not see the point of this. Shall we put equivalent disclaimers
into every single construct that consumes shared memory? There is no
such paragraph under LOCK TABLE, for example.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-27 22:52:15 | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |
| Previous Message | Neil Conway | 2006-11-27 22:45:00 | Re: Storing a dynahash for an entire connection or |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-27 22:52:15 | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |
| Previous Message | Joseph Shraibman | 2006-11-27 22:08:45 | doc patch for savepoints |