| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Details of how temp_buffers are actually used would be nice |
| Date: | 2017-08-30 18:53:10 |
| Message-ID: | CADK3HHLzTPtOjj2ipcwF0yTsr6RC9Xtvxjno0-Cv=_c0nGtVmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 30 August 2017 at 14:46, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Tue, Jun 27, 2017 at 03:43:22PM +0000, davecramer(at)gmail(dot)com wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.6/static/sql-deallocate.html
> > Description:
> >
> > It's not clear that temp_buffers determine the size of a temp table
> that
> > will be entirely in memory.
>
> Well, it depends what other temp tables are being accessed in the
> session as to whether the table is completely in temp_buffers or
> overflows to disk.
>
> Interesting. So can the details of how this works be made clearer?
Dave Cramer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2017-08-31 00:09:10 | Re: Row Level Security Policies documentation doesn't mention lack of support for views |
| Previous Message | Bruce Momjian | 2017-08-30 18:46:35 | Re: Details of how temp_buffers are actually used would be nice |