Обсуждение: [DOCS] Details of how temp_buffers are actually used would be nice
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.
On Tue, Jun 27, 2017 at 03:43:22PM +0000, davecramer@gmail.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. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
On 30 August 2017 at 14:46, Bruce Momjian <bruce@momjian.us> wrote:
On Tue, Jun 27, 2017 at 03:43:22PM +0000, davecramer@gmail.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