PgSql
in [SQL]
|
Feel the amatory impulse About this mailing: You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Feat... 31 Jul 2010 21:38
Give your thingy staying charge About this mailing: You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Feat... 31 Jul 2010 15:04
[HACKERS] ANALYZE versus expression indexes with nondefault opckeytype I've been poking at the FTS problem example recently submitted by Artur Dabrowski. It contains an index declared like so: CREATE INDEX idx_keywords_ger ON search_tab USING gin (to_tsvector('german'::regconfig, keywords)); which can be queried like so select * from search_tab where to_tsvector('german', ... 31 Jul 2010 12:54
rbtree code breaks GIN's adherence to maintenance_work_mem On Sat, Jul 31, 2010 at 12:40 AM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Another misbehavior that I noted while playing with Artur's example is that, while GIN index build seems to adhere pretty well to whatever maintenance_work_mem limit you give it in 8.4, it blows right by that limit in 9.0 and HEAD --- I o... 1 Aug 2010 01:56
Don't let your libido decrease About this mailing: You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Feat... 31 Jul 2010 11:48
ANALYZE versus expression indexes with nondefault opckeytype Stephen Frost <sfrost(a)snowman.net> writes: * Tom Lane (tgl(a)sss.pgh.pa.us) wrote: After a bit of study of the code, it appears to me that it's not too difficult to fix: we just have to use the expression's result type rather than the index column's atttypid in the subsequent processing. ANALYZE never ... 1 Aug 2010 17:00
[HACKERS] More fun with GIN lossy-page pointers I fixed the problem I was on about earlier with ginget.c doing the wrong thing for keystreams like this: ... ... 42/6 42/65535 42/7 ... ... (To recap, after reporting the potential lossy match for 42/6, the previous code would advance both keystreams and thus fail to see the potential lossy match for... 31 Jul 2010 10:42
review: xml_is_well_formed On fre, 2010-07-30 at 12:50 +0100, Mike Fowler wrote: * xml_is_well_formed returns true for simple text postgres=# SELECT xml_is_well_formed('ssss'); xml_is_well_formed -------------------- t (1 row) it is probably wrong result - is it ok?? Yes this is OK... 6 Aug 2010 14:53
ANALYZE versus expression indexes with nondefaultopckeytype * Tom Lane (tgl(a)sss.pgh.pa.us) wrote: After a bit of study of the code, it appears to me that it's not too difficult to fix: we just have to use the expression's result type rather than the index column's atttypid in the subsequent processing. ANALYZE never actually looks at the index column contents (indee... 1 Aug 2010 04:04
[HACKERS] rbtree code breaks GIN's adherence to maintenance_work_mem Another misbehavior that I noted while playing with Artur's example is that, while GIN index build seems to adhere pretty well to whatever maintenance_work_mem limit you give it in 8.4, it blows right by that limit in 9.0 and HEAD --- I observed it happily eating something north of 128MB with a maintenance_work_mem... 31 Jul 2010 01:05 |