pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedDetails of how temp_buffers are actually used would be nice
3+ messages / 3 participants
[nested] [flat]
* Details of how temp_buffers are actually used would be nice
@ 2017-06-27 15:43 davecramer@gmail.com
0 siblings, 1 reply; 3+ messages in thread
From: davecramer@gmail.com @ 2017-06-27 15:43 UTC (permalink / raw)
To: pgsql-docs
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.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Details of how temp_buffers are actually used would be nice
@ 2017-08-30 18:46 Bruce Momjian <bruce@momjian.us>
parent: davecramer@gmail.com
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Momjian @ 2017-08-30 18:46 UTC (permalink / raw)
To: davecramer@gmail.com; +Cc: pgsql-docs
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 +
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Details of how temp_buffers are actually used would be nice
@ 2017-08-30 18:53 Dave Cramer <davecramer@gmail.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 3+ messages in thread
From: Dave Cramer @ 2017-08-30 18:53 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: pgsql-docs
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-08-30 18:53 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-06-27 15:43 Details of how temp_buffers are actually used would be nice davecramer@gmail.com
2017-08-30 18:46 ` Bruce Momjian <bruce@momjian.us>
2017-08-30 18:53 ` Dave Cramer <davecramer@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox