[BUGS] BUG #6702: SELECT Query on INDEX

2012-06-22 Thread alokrawat0212
The following bug has been logged on the website: Bug reference: 6702 Logged by: Alok Rawat Email address: alokrawat0...@gmail.com PostgreSQL version: 9.1.0 Operating system: WIN 7 Description: Hello all, I created a Index in postgres.Now i want to fire select query

Re: [BUGS] BUG #6702: SELECT Query on INDEX

2012-06-22 Thread Ryan Kelly
On Fri, Jun 22, 2012 at 01:19:50AM +, alokrawat0...@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 6702 > Logged by: Alok Rawat > Email address: alokrawat0...@gmail.com > PostgreSQL version: 9.1.0 > Operating system: WIN 7 > Descrip

Re: [BUGS] BUG #6702: SELECT Query on INDEX

2012-06-22 Thread Kevin Grittner
wrote: > I created a Index in postgres.Now i want to fire select query in > this Index and check data. > > Please tell me how to perform this??? This is not a bug. Please post any follow-ups or similar questions to pgsql-general or pgsql-novice; or if it is a performance question, try pgsql-

[BUGS] BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations

2012-06-22 Thread jeff
The following bug has been logged on the website: Bug reference: 6704 Logged by: Jeff Frost Email address: j...@pgexperts.com PostgreSQL version: 9.1.4 Operating system: Windows and Linux Description: DROP and CREATE extension appear to work fine, but if you ALTER EXT

Re: [BUGS] BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations

2012-06-22 Thread Tom Lane
j...@pgexperts.com writes: > DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION > postgis SET SCHEMA foo, it leaves a few relations behind. What it seems to be leaving behind is indexes ... also relation rowtypes. A bit of looking shows that ALTER EXTENSION SET SCHEMA calls

Re: [BUGS] BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations

2012-06-22 Thread Jeff Frost
On Jun 22, 2012, at 7:37 PM, Tom Lane wrote: > j...@pgexperts.com writes: >> DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION >> postgis SET SCHEMA foo, it leaves a few relations behind. > > What it seems to be leaving behind is indexes ... also relation rowtypes. > > A