On 2/2/15 9:37 PM, Slava Mudry wrote:
On Mon, Feb 2, 2015 at 5:52 PM, Jim Nasby mailto:jim.na...@bluetreble.com>> wrote:
On 2/2/15 7:36 PM, Jim Nasby wrote:
Currently the fact that it needs to go back to old tables
and FTS them
every 2B transactions (or
On Mon, Feb 2, 2015 at 5:52 PM, Jim Nasby wrote:
> On 2/2/15 7:36 PM, Jim Nasby wrote:
>
>>
>>> Currently the fact that it needs to go back to old tables and FTS them
>>> every 2B transactions (or rely on autovacuum for this) and you can't do
>>> anything about it (like permanently freeze the tab
On 2/2/15 7:36 PM, Jim Nasby wrote:
Currently the fact that it needs to go back to old tables and FTS them
every 2B transactions (or rely on autovacuum for this) and you can't do
anything about it (like permanently freeze the tables) seems like a big
scalability issue. Does it not?
Unfortunate
On 2/1/15 3:08 PM, Josh Berkus wrote:
On 01/30/2015 05:34 PM, Jim Nasby wrote:
On 1/30/15 2:26 PM, Josh Berkus wrote:
This would probably work because there aren't a lot of data structures
where people would have the same key:value pair in different locations
in the JSON, and care about it stat
On 2/2/15 7:01 PM, Slava Mudry wrote:
Please don't top-post. It's much better to answer questions inline in an
email.
I am running PostgreSQL 9.3.2 on linux. Freeze values are defaults.
We cannot rely on autovacuum on our current hardware, so it's turned
down to 2 workers with naptime=10min.
On Tue, Jan 27, 2015 at 1:06 AM, Josh Berkus wrote:
> Folks,
>
> Currently, JSONB fields don't have statistics, and estimate a flat 1%
> selectivity. This can result in poor query plans, and I'm wondering if
> anyone has a suggested workaround for this short of hacking a new
> selectivity functio
AlexK987 writes:
>>> I've created a GIN index on an INT[] column, but it slows down the selects.
>>> Here is my table:
>>
>>> create table talent(person_id INT NOT NULL,
>>> skills INT[] NOT NULL);
>>
>>> insert into talent(person_id, skills)
>>> select generate_series, array[0, 1] || generate_ser
AlexK987 writes:
>> I've created a GIN index on an INT[] column, but it slows down the selects.
>> Here is my table:
>
>> create table talent(person_id INT NOT NULL,
>> skills INT[] NOT NULL);
>
>> insert into talent(person_id, skills)
>> select generate_series, array[0, 1] || generate_series
>> f
