Hi,
there are many Hash and Merge joins that may generate a lot of temp space,
it could also be a problem of forgotten column in the join.
Could you also provide indexes definitions (pk, uk and others)
with the EXPLAIN (ANALYZE BUFFERS)
(you can limit the scope of the query to help it to finish
Thanks,
Yes I will be busy with pg 10 new features testing ;o)
Nb: I also have installed a unix partition to be able to test non-core
extensions and prototypes
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing
I saw a similar project on oracle that was storing (long) messages (clob).
Partionning by creation date was in place, as btree indexes to access data
per id. It was working fine for inserts, as for sélect, but purges (delete)
where not freeing space. In fact rétention was not the same for all
What is the (min, max, avg) size of the inserted text ?
-
PAscal
SQLeo projection manager
Senior Oracle dba migrating towards PostgreSQL
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing list
DELETE FROM table_with_duplicates AS T1 USING table_with_duplicates AS T2
WHERE
T1.column_1 = T2.column_1
AND T1.column_2 = T2.column_2
AND T1.column_3 = T2.column_3
AND T1.row_num < T2.row_num
--
Sent from:
Hello,
Using PG mainly on windows, I would have liked to test new releases /
development versions before they are available in
https://www.postgresql.org/download/windows/
Are there some build farms or places where I could find "build snapshots for
windows" without having to build them by
No
You should try with 2 single column indexes and may be rewrite your query
with a Union All syntax
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription: