pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
tablespaces and ramdisks 2+ messages / 2 participants [nested] [flat]
* tablespaces and ramdisks @ 2004-08-09 15:29 Merlin Moncure <merlin.moncure@rcsonline.com> 0 siblings, 1 reply; 2+ messages in thread From: Merlin Moncure @ 2004-08-09 15:29 UTC (permalink / raw) To: pgsql-performance If you use tablespaces to put a high-update, non-critical table on a ramdisk, will updates to that table will still cause the WAL files to sync? I'm looking for a way to turn off syncing completely for a table. Temporary tables do this, but they can only be accessed from a single backend. Merlin ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: tablespaces and ramdisks @ 2004-08-09 16:35 Tom Lane <tgl@sss.pgh.pa.us> parent: Merlin Moncure <merlin.moncure@rcsonline.com> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2004-08-09 16:35 UTC (permalink / raw) To: Merlin Moncure <merlin.moncure@rcsonline.com>; +Cc: pgsql-performance "Merlin Moncure" <merlin.moncure@rcsonline.com> writes: > If you use tablespaces to put a high-update, non-critical table on a > ramdisk, will updates to that table will still cause the WAL files to > sync? Sure. Postgres has no way of knowing that there's anything special about such a tablespace. > I'm looking for a way to turn off syncing completely for a table. There isn't one, and I'm not eager to invent one. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-08-09 16:35 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2004-08-09 15:29 tablespaces and ramdisks Merlin Moncure <merlin.moncure@rcsonline.com> 2004-08-09 16:35 ` Tom Lane <tgl@sss.pgh.pa.us>
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