tis 2017-04-25 klockan 23:19 -0400 skrev Alessandro Ferrucci:
> After about 40 inutes the slow query finally finished and the result
> of the EXPLAIN plan can be found here:
>
>
> https://explain.depesz.com/s/BX22
>
>
> Thanks,
> Alessandro Ferrucci
I'm not so familiar with the index implement
On 26 April 2017 at 15:19, Alessandro Ferrucci
wrote:
> After about 40 inutes the slow query finally finished and the result of the
> EXPLAIN plan can be found here:
>
> https://explain.depesz.com/s/BX22
> Index Scan using field_unit_id_idx on field (cost=0.00..8746678.52
> rows=850149 width=8)
After about 40 inutes the slow query finally finished and the result of the
EXPLAIN plan can be found here:
https://explain.depesz.com/s/BX22
Thanks,
Alessandro Ferrucci
On Tue, Apr 25, 2017 at 11:10 PM, Alessandro Ferrucci <
alessandroferru...@gmail.com> wrote:
> Hello - I am migrating a curre
Hello - I am migrating a current system to PostgreSQL and I am having an
issue with a relatively straightforward query being extremely slow.
The following are the definitions of the tables:
CREATE TABLE popt_2017.unit
(
id serial NOT NULL,
unit_id text,
batch_id text,
create_date timestam
On 04/25/2017 08:28 AM, Johann Spies wrote:
On 24 April 2017 at 15:17, Tomas Vondra wrote:
On 04/24/2017 08:48 AM, Johann Spies wrote:
Why would the planner prefer the use the gin index and not the btree
index in this case?
You'll need to show what queries are you running - that's a quite
On Tue, Apr 25, 2017 at 1:17 AM, Andres Freund wrote:
> Questions (answer as many you can comfortably answer):
> - How many MB/s, segments/s do you see on busier servers?
~20MB/s with FPW compression, with peaks of ~35MB/s. Writes become the
bottleneck without compression and it tops at about 40-
On Mon, Apr 24, 2017 at 9:17 PM, Andres Freund wrote:
>
> Questions (answer as many you can comfortably answer):
> - How many MB/s, segments/s do you see on busier servers?
> - What generates the bulk of WAL on your servers (9.5+ can use
> pg_xlogdump --stats to compute that)?
> - Are you seein
Hi Andres.
> 25 апр. 2017 г., в 7:17, Andres Freund написал(а):
>
> Hi,
>
> I've lately seen more and more installations where the generation of
> write-ahead-log (WAL) is one of the primary bottlenecks. I'm curious
> whether that's primarily a "sampling error" of mine, or whether that's
> ind
On 25 April 2017 at 18:28, Johann Spies wrote:
> On 24 April 2017 at 15:17, Tomas Vondra wrote:
>> On 04/24/2017 08:48 AM, Johann Spies wrote:
>>>
>>>
>>> Why would the planner prefer the use the gin index and not the btree
>>> index in this case?
>>>
>>
>> You'll need to show what queries are yo
