Re: [SQL] postgres 7.1.3: why does the query plan ignore indexes?
Bruce Momjian <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Bruce Momjian <[EMAIL PROTECTED]> writes: >>> Should we consider adding some warning when someone creates an index on >>> an int2 column? >> >> I don't think so. Better to expend our energy on solving the >> fundamental problem. > I am thinking _until_ we fix the problem. Is it actually hard to add? Why int2 in particular? And not int8? float4? Or numeric, float8, or int4 in the wrong contexts? How about bpchar or varchar? I figure we can waste at least as much time arguing about when/where/why to issue warnings as it will take to solve the real problem. regards, tom lane ---(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
[SQL] How to return a record set from function.
Dear Friends, I am newbie to Postgres. I am running 7.3.4 on Linux 7.3. I am using Pgadmin tool. I need to return the table rows via record set. Create table t1 (c1 int, c2 varchar, c3 varchar); Create or Replace function sel_t1 () returns setof records as ' select c1, c2, c3 from t1; ' Language SQL; It was fine and created a function. while i execute it as select sel_t1; I got the following error. ERROR: Cannot display a value of type RECORD How to solve this. Please help. Kumar
Re: [SQL] postgres 7.1.3: why does the query plan ignore indexes?
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Should we consider adding some warning when someone creates an index on > > an int2 column? > > I don't think so. Better to expend our energy on solving the > fundamental problem. I am thinking _until_ we fix the problem. Is it actually hard to add? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[SQL] Canceling other backend's query
Hi, Can i cancel querys runing on other backends, or disconnect a client from the server? I can kill the backend process, but sometimes this causing shared memory troubles. DAQ ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings