> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > I think the current implementaion in utf8_and_iso8859.c is fast but
> > too fragile against rearranging of encoding id. I modify those functions
> > in utf8_and_iso8859.c to do a linear search with encoding id.
>
> That's not unreasonable, but I was w
daveg <[EMAIL PROTECTED]> writes:
> I don't understand the motivation for so many connections by default, it
> seems wasteful in most cases.
I think Andrew is thinking about database-backed Apache servers ...
Some quick checks say that CVS tip's demand for shared memory increases
by about 26kB pe
daveg wrote:
On Fri, Dec 23, 2005 at 03:38:56PM -0500, Andrew Dunstan wrote:
What numbers would you like? If what I suggested seems odd, how about
targets of 400 connections, 4000 shared_buffers and 200,000
max_fsm_pages?
Here's a patch that does what I had in mind. On my modest wo
On Fri, Dec 23, 2005 at 03:38:56PM -0500, Andrew Dunstan wrote:
> >
> >What numbers would you like? If what I suggested seems odd, how about
> >targets of 400 connections, 4000 shared_buffers and 200,000
> >max_fsm_pages?
>
>
> Here's a patch that does what I had in mind. On my modest workstati
er patch attached this time
Andrew Dunstan wrote:
I wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Nearly everyone seems to agree that the default for max_fsm_pages
is woefully low, so I would like to have the default for this set
unconditionally to 200,000 rat
I wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Nearly everyone seems to agree that the default for max_fsm_pages is
woefully low, so I would like to have the default for this set
unconditionally to 200,000 rather than 20,000. The cost would be
just over 1Mb of sh
Here's a new try. This one touches to pg_dump side too - for v3
COPY functions usage instead of deprecated ones.
I'd be so appreciated if somebody can review attached patch.
Regards.
Index: src/backend/commands/copy.c
===
RCS file:
