btw, 9.4 should be wiser in case of rare+common terms,
thanks to GIN fast scan feature.
I'll look forward to it! We have a few other GIN indexes . . .
I don't want to misrepresent my impression of Postgres performance; the only
other case where I've made a significant improvement by tweaking w
btw, 9.4 should be wiser in case of rare+common terms, thanks to GIN
fast scan feature.
On Sun, Apr 20, 2014 at 8:30 AM, Laurence Parry wrote:
> As mentioned here and elsewhere (most recently in "How can I get the query
> planner to use a bitmap index scap instead of an index scan ?" - 8 Mar
> 20
As mentioned here and elsewhere (most recently in "How can I get the query
planner to use a bitmap index scap instead of an index scan ?" - 8 Mar
2014), estimation of the relative cost of text search operations using
GIN-indexed columns sometimes goes awry, particularly when there will be a
lar
Does anyone have some good tricks for mapping IP addresses to ASN numbers in
very large volumes?
This is probably more a "how would you approach this problem?" than "can you
help me tweak this query"
I have a very large number of IP addresses (many millions) that are found in
some security re
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
Hello,
If a table contains simple fields as well as large (hundreds of KiB)
text fields, will accessing only the simple fields cause the entire
record data, including the large fields, to be read and unpacked?
(e.g. SELECT int_field FROM table_with_large_text)
More details: after thinking about i
