Re: [PERFORM] investigating slow queries through pg_stat_activity

feature. For example, if you set it to 250 then all SQL statements that run 250ms or longer will be logged. Enabling this option can be useful in tracking down unoptimized queries in your applications. Only superusers can change this setting. George Essig ---(end of broadc

Re: [PERFORM] SELECT DISTINCT Performance Issue

ndexes. If the the column is an integer, it would not be possible to have a value like 'arbitrary value that looks nothing like an integer'. George Essig ---(end of broadcast)--- TIP 6: Have you searched our list archi

Re: [PERFORM] SELECT DISTINCT Performance Issue

> Is PlayerID an integer datatype or a text datatype. It seems like PlayerID should be an integer data type, but postgres treats PlayerID as a text data type. This is because the value '0' is quoted in your query. Also, the explain analyze output shows &q

Re: [PERFORM] int4 in a GiST index

earch2 to create a multicolumn index on the in4 and the tsvector columns. See the following for an example: http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/oscon_tsearch2/multi_column_index.html George Essig ---(end of broadcast)--- TIP

Re: [PERFORM] TSearch2 and optimisation ...

ex, see: http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/oscon_tsearch2/multi_column_index.html There are no easy answers. Like I said, performance tuning must be done on a case by case basis. Hope this helps, George Essig ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [PERFORM] TSearch2 and optimisation ...

rch/V2/docs/oscon_tsearch2/stop_words.html Multicolumn GiST index http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/oscon_tsearch2/multi_column_index.html openfts-general mailing list archive http://sourceforge.net/mailarchive/forum.php?forum=openfts-general Try some of things out an

Re: [PERFORM] High Performance/High Reliability File system on SuSE64

d higher loads, XFS can provide the best overall performance. George Essig ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [PERFORM] INSERT extremely slow with large data sets (fwd)

> VACUUM ANALYZE will reclaim disk space and update statistics used by the optimizer to help execute queries faster. This could speed up your inserts. See http://www.postgresql.org/docs/7.3/static/sql-vacuum.html. George Essig ---(end of broadcast)

Re: [PERFORM] INSERT extremely slow with large data sets (fwd)

one row into a table when there are only few rows present and when > there > are thousands: Try running VACUUM ANALYZE periodically during inserts. I found this to help. George Essig ---(end of broadcast)--- TIP 3: if posting/reading thr

Re: [PERFORM] TPC-R benchmarks

scan. If this is the case, it would be safer to chose a small value for random_page_cost. George Essig ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match