Re: [GENERAL] Disable an index temporarily

On Apr 19, 2014 1:53 PM, "Torsten Förtsch" wrote: > > Hi, > > an index can be INVALID (pg_index.indisvalid=false). > > I want to temporarily disable an index so that it won't be used to > access data but will still be updated. > > Can I simply set pg_index.indisvalid=false and later turn it true a

Re: [GENERAL] Could use some advice on search architecture

the other is named imcs. imcs is mainly a memory database,it is very fast for olap,because of multi threads parallel query plan and column storage.for billions of data,most group by like querys return within 2s. we use it for several weeks and happy for the performance. jov 在 2014-4-19 下午8:27，"Dor

[GENERAL] Re: [PERFORM] Hot standby 9.2.1 PANIC: WAL contains references to invalid pages

On Fri, Apr 18, 2014 at 1:23 AM, Vishalakshi Navaneethakrishnan wrote: > if i change the wal level as archive, then this problem will go..? We are > just using warm stand by. so shall we change the wal_level as archive..? Can > you please reply this mail as soon as possible? AFAIK, the problem ap

Re: [GENERAL] Could use some advice on search architecture

Because this is a topic that interests me I have done some digging. MonetDB is a proper column-store DBMS. It is used on some decent sized projects, several of which are EU-funded. Digging a bit deeper I have discovered that a PostgreSQL Foreign Data Wrapper for M

[GENERAL] Disable an index temporarily

Hi, an index can be INVALID (pg_index.indisvalid=false). I want to temporarily disable an index so that it won't be used to access data but will still be updated. Can I simply set pg_index.indisvalid=false and later turn it true again? Thanks, Torsten -- Sent via pgsql-general mailing list (

Re: [GENERAL] Could use some advice on search architecture

>On 04/19/2014 06:26 AM, Ron Pasch wrote: >> > - It should be possible to search for products and provide properties >> > that the product SHOULD have, not must have. >>> >>> I don't understand this. Say you have a sprocket in red and green. Do you >>> want to search for: >>> >>> select * from

Re: [GENERAL] Could use some advice on search architecture

On 04/19/2014 06:26 AM, Ron Pasch wrote: > - It should be possible to search for products and provide properties > that the product SHOULD have, not must have. I don't understand this. Say you have a sprocket in red and green. Do you want to search for: select * from product where name = '

Re: [GENERAL] Could use some advice on search architecture

Postgresql has 2 column store, 1-in memory(cant remember the name) and http://www.citusdata.com/blog/76-postgresql-columnar-store-for-analytics On Sat, Apr 19, 2014 at 2:10 PM, Robin wrote: > bottom post > On 19/04/2014 12:46, R. Pasch wrote: > > On 19-4-2014 9:38, Robin wrote: > > > Well, giv

Re: [GENERAL] Could use some advice on search architecture

bottom post On 19/04/2014 12:46, R. Pasch wrote: On 19-4-2014 9:38, Robin wrote: Well, given that there are known limited attributes, this is the type of application that really really suits a column oriented database, such as Sybase IQ (now sold by SAP). Its a neat product that scales. Grea

Re: [GENERAL] Could use some advice on search architecture

Hi, Seems that this blog post is worth reading in your case http://hlinnaka.iki.fi/2014/03/28/gin-as-a-substitute-for-bitmap-indexes/ regards, Marc Mamin Von: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org]" im Auftrag von "Robin

[GENERAL] Patched odbc_dfw for PG >= 9.2

Heillo, after stumbling across compile errors for odbc_fdw I realised it was still on the 9.1. level. I've patched it, based on the tds_fdw code (so it's still read-only). It does compile, and I think it is generally sane, however I'm _anything but a C hacker_, so whoever feels confident eno

Re: [GENERAL] Could use some advice on search architecture

On 18/04/2014 21:24, Andy Colson wrote: On 4/18/2014 8:59 AM, Ron Pasch wrote: Hello, I'm contemplating what architecture I should use to make searching as fast as possible given the information available and the search requirements. Let me give some background first; - The database contains