Hello
I have a bad query on PostgreSQL 9.0.23 - 64bit - Windows 2012 R2 - 48GB Ram
explain analyze select d.data_id, d.table_name, d.event_type, d.row_data,
d.pk_data, d.old_data, d.create_time, d.trigger_hist_id, d.channel_id,
d.transaction_id, d.source_node_id, d.external_data, '' from
On 02/20/2016 08:46 AM, tuanhoanganh wrote:
Hello
I have a bad query on PostgreSQL 9.0.23 - 64bit - Windows 2012 R2 - 48GB Ram
explain analyze select d.data_id, d.table_name, d.event_type,
d.row_data, d.pk_data, d.old_data, d.create_time, d.trigger_hist_id,
d.channel_id, d.transaction_id,
Adrian Klaver writes:
> Took liberty of reformatting the above here:
> ...
> FROM
> sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP'
> AND d.data_id BETWEEN g.start_id
> AND g.end_id
> WHERE
> d.channel_id = 'sale_transaction'
> ORDER BY
>
On Sat, Feb 20, 2016 at 7:13 PM, Adrian Klaver
wrote:
.
> FROM
> sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP'
> AND d.data_id BETWEEN g.start_id
> AND g.end_id
.
> The thing that stands out to me is that I do not see that sym_data and
>
On Sat, Feb 20, 2016 at 7:37 PM, Tom Lane wrote:
> It looks like the bitmap heap scan generally returns exactly one row for
> each outer row, which makes me wonder if the BETWEEN couldn't be replaced
> with some sort of equality.
Mm, I'm not good reading explains, but that
On 02/20/2016 10:39 AM, Francisco Olarte wrote:
On Sat, Feb 20, 2016 at 7:13 PM, Adrian Klaver
wrote:
.
FROM
sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP'
AND d.data_id BETWEEN g.start_id
AND g.end_id
.
The thing that stands out to
On Sat, Feb 20, 2016 at 8:46 AM, tuanhoanganh wrote:
> Hello
>
> I have a bad query on PostgreSQL 9.0.23 - 64bit - Windows 2012 R2 - 48GB Ram
9.0 is no longer supported. You should work toward upgrading to a
newer version. It might not solve this problem, but it would give