[PERFORM] Cost of INSERT rules

before doing the update ? cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http

[PERFORM] Performance on writable views

about that issue ? cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de

[PERFORM] Implementing an regex filter

-- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce

[PERFORM] Index + mismatching datatypes [WAS: index on custom function; explain]

. Of course I tried to use casted index (aka ON (foo::oid)), but it didn't work. What am I doing wrong ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax

Re: [PERFORM] Massive delete performance

increase this DELETE procedure because it is really slow??? There are of corse a lot of data's to be deleted. Have you set up the right indices ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207

Re: [PERFORM] plain inserts and deletes very slow

application is the only one writing directly to this table. cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email

Re: [PERFORM] Select performance vs. mssql

-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] - Realtime

Re: [PERFORM] Need help to decide Mysql vs Postgres

is a friendly guy. Is there anything similar for java ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL

Re: [PERFORM] Why the planner is not using the INDEX .

and then execute it. BTW: why isn't IN not usable with arrays ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email

Re: [PERFORM] plain inserts and deletes very slow

is your method for running the query 'manually'. Are you running it locally or from a remote machine or what? using psql remotely - database and client machines are sitting on the same wire. cu -- - Enrico Weigelt== metux

Re: [PERFORM] plain inserts and deletes very slow

* Alvaro Herrera [EMAIL PROTECTED] wrote: On Mon, Jul 04, 2005 at 02:17:47AM +0200, Enrico Weigelt wrote: * David Mitchell [EMAIL PROTECTED] wrote: Perhaps if you are doing a lot of inserts and deletes, vacuuming every 6 minutes would be closer to your mark. Try vacuuming every 15

Re: [PERFORM] investigating slow queries through pg_stat_activity

to encapsulate the queries into views - this makes logging and tracking down problems much easier. cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax

[PERFORM] plain inserts and deletes very slow

-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] - Realtime

Re: [PERFORM] plain inserts and deletes very slow

* Steinar H. Gunderson [EMAIL PROTECTED] wrote: On Mon, Jul 04, 2005 at 12:45:37AM +0200, Enrico Weigelt wrote: my application reads and writes some table quite often (multiple times per second). these tables are quite small (not more than 20 tuples), but the operations take quite a long

Re: [PERFORM] plain inserts and deletes very slow

* Enrico Weigelt [EMAIL PROTECTED] wrote: forgot to mention: + linux-2.6.9 + postgres-7.4.6 + intel celeron 2ghz + intel ultra ata controller + 768mb ram cu -- - Enrico Weigelt== metux IT service

Re: [PERFORM] plain inserts and deletes very slow

-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] - Realtime Forex/Stock Exchange trading

Re: [PERFORM] plain inserts and deletes very slow

into shape after them slowing down as they have). hmm. I've just done vacuum full at the moment on these tables, but it doesnt seem to change anything :( cu -- - Enrico Weigelt== metux IT service phone: +49 36207

Re: [PERFORM] BLOB's bypassing the OS Filesystem for better Image loading speed?

reasons to put images into the database, ie. if some clients directly work on db connections and all work (including image upload) should be done over the db link. cu -- - Enrico Weigelt== metux IT service phone: +49

[PERFORM] index on different types

casting required ? thx -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED

[PERFORM] index not used

where id = 2; I've got only 15 records in this table, but I wanna have it as fast as possible since its used (as a map between IDs and names) for larger queries. thx -- - Enrico Weigelt== metux IT service phone

Re: [PERFORM] immutable functions vs. join for lookups ?

in practise (or at most there will be an insert once a year) isnt there any way to enforce the function to be really immutable ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http

Re: [PERFORM] immutable functions vs. join for lookups ?

should I use ? Is a join better than a function ? cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL

[PERFORM] foreign key performance

Hi folks, do foreign keys have any influence on performance (besides slowing down huge inserts) ? do they bring any performance improvement ? thx -- - Enrico Weigelt== metux IT service phone: +49 36207 519931

Re: [PERFORM] immutable functions vs. join for lookups ?

* Tom Lane [EMAIL PROTECTED] wrote: Enrico Weigelt [EMAIL PROTECTED] writes: c) CREATE FUNCTION id2username(oid) RETURNS text LANGUAGE 'SQL' IMMUTABLE AS ' SELECT username AS RESULT FROM users WHERE uid = $1'; This is simply dangerous. The function is *NOT* immutable

Re: [PERFORM] clear function cache (WAS: SQL function inlining)

* Stephan Szabo [EMAIL PROTECTED] wrote: On Thu, 24 Mar 2005, Enrico Weigelt wrote: * Alvaro Herrera [EMAIL PROTECTED] wrote: On Thu, Mar 24, 2005 at 02:32:48PM +0100, Enrico Weigelt wrote: BTW: is it possible to explicitly clear the cache for immutable functions ? What

[PERFORM] immutable functions vs. join for lookups ?

-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49 174 7066481

[PERFORM] clear function cache (WAS: SQL function inlining)

is quite unpredictable. thx -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49

Re: [PERFORM] View columns calculated

-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49 174 7066481 - -- DSL ab 0 Euro

Re: [PERFORM] clear function cache (WAS: SQL function inlining)

* Alvaro Herrera [EMAIL PROTECTED] wrote: On Thu, Mar 24, 2005 at 02:32:48PM +0100, Enrico Weigelt wrote: BTW: is it possible to explicitly clear the cache for immutable functions ? What cache? There is no caching of function results. Not ? So what's immutable for ? snip I'd like