On Tue, Aug 23, 2005 at 12:38:04PM -0700, Josh Berkus wrote:
which have a clear and measurable effect on performance and are fixable without bloating the PG code. Some of these issues (COPY path, context switching
Does that include increasing the size of read/write blocks? I've noticed that with a large enough table it takes a while to do a sequential scan, even if it's cached; I wonder if the fact that it takes a million read(2) calls to get through an 8G table is part of that. Mike Stone ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
