Yes I did do analyze the here is the get_pwd function
-- Function: public.get_pwd(varchar, varchar, varchar, varchar)
-- DROP FUNCTION public.get_pwd(varchar, varchar, varchar, varchar);
CREATE OR REPLACE FUNCTION public.get_pwd(varchar, varchar, varchar,
varchar)
RETURNS varchar AS
'
DECL
On Wednesday 07 April 2004 16:59, Andrew McMillan wrote:
> One thing I recommend is to use ext2 (or almost anything but ext3).
> There is no real need (or benefit) from having the database on a
> journalled filesystem - the journalling is only trying to give similar
> sorts of guarantees to what th
Hey,
Has anyone done performance tests for OpenFTS on a really large database? I
was speaking at PerlMongers and somebody asked.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 6: Have you searched our list
"Patrick Hatcher" <[EMAIL PROTECTED]> writes:
> Doing an upgrade from 7.3.6 to 7.4.2 and I keep seeing the recycled
> transaction log about every 2 mins. For future upgrades, is there
> something that can be set so that I don't have as many recycles?
Increasing checkpoint_segments ... but you se
Doing an upgrade from 7.3.6 to 7.4.2 and I keep seeing the recycled
transaction log about every 2 mins. For future upgrades, is there
something that can be set so that I don't have as many recycles? It seems
to slow down the importing of data.
Here's my current settings:
#--
Ken Geis <[EMAIL PROTECTED]> writes:
> Does anyone think that the planner issue has merit to address? Can
> someone help me figure out what code I would look at?
The planner doesn't currently attempt to "drill down" into a sub-select-
in-FROM to find statistics about the variables emitted by the
Grega,
> Well, as I said, that's why I was asking - I'm willing to give it a go
> if nobody can prove me wrong. :)
Why not? If you have time?
> I thought you knew - OCFS, OCFS-Tools and OCFSv2 have not only been open-
> source for quite a while now - they're released under the GPL.
Keen! Wo
"Andrew Matthews" <[EMAIL PROTECTED]> writes:
> [ PG 7.3.4 much slower than 7.2.1 ]
>
> Both have same databases, Both have had vacume full ran on them.
You did ANALYZE too, right?
The bulk of the time is evidently going into the seqscan on users in
each case:
> -> Seq Scan
