| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | "Raymond O'Donnell" <rod(at)iol(dot)ie>, hmidi slim <hmidi(dot)slim2(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Notify client when a table was full |
| Date: | 2018-01-21 18:31:17 |
| Message-ID: | CA+bJJbwjY0cB09sNs8uh31Z1dFgtfsaej4bb1W1nHkXsoi8mOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jan 21, 2018 at 1:27 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Jan 19, 2018 at 03:40:01PM +0000, Raymond O'Donnell wrote:
...
>> How do you define "full"?
> There could be two definitions here:
> 1) A table contains more data than a customly-defined amount of data
> on-disk.
> 2) The partition where the table data is located runs out of disk
> space.
I see a third definition. No more rows can be inserted without
previously deleting. The simplest case I can think of is "b boolean
primary key" with two rows already in.
But I doubt the OP was referring to any of that.
Francisco Olarte
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincenzo Romano | 2018-01-21 18:44:07 | Re: Notify client when a table was full |
| Previous Message | Rafał Zabrowarny | 2018-01-21 13:40:03 | License question regarding distribution of binaries |