Re: [GENERAL] Improve Search

. Thanks. > Date: Thu, 1 Nov 2007 22:32:47 -0500 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [GENERAL] Improve Search > CC: pgsql-general@postgresql.org > > On 11/1/07, carter ck wrote: >> >> Hi al

[GENERAL] Improve Search

Hi all, Has anyone come across a solution for faster and powerful search stored procedure in a table that contains more than 500K of records? I am currently trying to work around with it. All helps are appreciated. Thanks. _ Exp

[GENERAL]

Hi all, I was trying to create function in postgres, but it returns error mentioning the language is NOT defined. The function is as following: CREATE OR REPLACE FUNCTION test_word_count(TEXT, TEXT) RETURNS INTEGER AS $$ DECLARE d_word ALIAS FOR $1; d_phrase ALIAS FOR $2; BEGIN IF d_word IS

Re: [GENERAL] Database Select Slow

Hi, Thanks for the clarification. It helps to resolve the problem. Now, the page can be fully loaded within 2 seconds. Thanks. From: "Scott Marlowe" <[EMAIL PROTECTED]> To: "carter ck" <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GE

[GENERAL] Database Select Slow

Hi all, I am facing a performance issue here. Whenever I do a count(*) on a table that contains about 300K records, it takes few minutes to complete. Whereas my other application which is counting > 500K records just take less than 10 seconds to complete. I have indexed all the essential col

Re: [GENERAL] Duplicate Key Violates Unique Contraint whenUpdating a table

kindly post a feedback. THanks. From: Ragnar <[EMAIL PROTECTED]> To: carter ck <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Duplicate Key Violates Unique Contraint whenUpdating a table Date: Sun, 24 Jun 2007 10:05:16 + On sun, 2007-06-24 at 16:55 +

[GENERAL] Duplicate Key Violates Unique Contraint when Updating a table

Hi all, I am experiencing thgis problem since this morning. I seldom heard about unique key constraint violation to happen when updating a table. It happens to 1 or few records at early stage, but then to all. My updating command is as following: update mytable set my_status='Y' where myid='

[GENERAL] Creating Index

Hi all, I am wonderring the differences between creating an index on several columns of a table and an index on each column of a table. For example, following is my select query: select * from my_table where myrowid='abc' and mytask='TEst 1' and myday!='holiday'; Which of the following is

[GENERAL] How to create an archive for old records?

Hi all, I am looking for ways to create an archive of records older than 3 months in one of my table, and store these extracted records into a local database. Does Postgres have any command to do this? Thanks. _ Find just what y

[GENERAL] Linking a Postgres table on Linux to Ms Access

Hi all, Is there any way that I can synchronize a table in Postgres on Linux with another table in Ms Access? The requirement of the assignment is as following: In postgres, there is a table called message_received. Whenever we insert, update or edit this table, the table in Ms Access should

Re: [GENERAL] Improve Postgres Query Speed

Hi, the rpt_generated is a boolean value. And you are definitely right when updating the table. The time it takes is getting longer and longer. When I do a select statement, the speed has also degraded. Thanks. From: Jorge Godoy <[EMAIL PROTECTED]> To: "carter ck" <[E

Re: [GENERAL] Improve Postgres Query Speed

" btree (msg_status) Thanks for help. From: "Chad Wagner" <[EMAIL PROTECTED]> To: "carter ck" <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Improve Postgres Query Speed Date: Mon, 15 Jan 2007 19:54:51 -0500 On 1/15/07, carter ck <

[GENERAL] Improve Postgres Query Speed

Hi all, I am having slow performance issue when querying a table that contains more than 1 records. Everything just slow down when executing a query though I have created Index on it. Can anyone suggest ways to improve the speed? Thanks. ___

[GENERAL] IS it a good practice to use SERIAL as Primary Key?

Hi all, I am wonderring if it is a good practice to use SERIAL index as primary key, as it is only available up to 999? Currently i am dealing with storing LDAP users into Postgres and i am looking for a better way to make use of the DN as primary key instead of SERIAL index. Any advic

[GENERAL] Postrgres Sequence Error

Hi all, Currently I am ancountering a sequnce error. THe sequence number is being used up to 573, but, suddenly and unexpectedly, when I issue the select nextval command, it gives the value of 400, which is currently occupied by a record. I am looking forward for any possible solution to sol