Re: brininsert optimization opportunity
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: James Wang <jwang25610@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-01-08T11:23:14Z
Lists: pgsql-hackers
On 2023-Dec-21, James Wang wrote: > Hi All, not sure how to "Specify thread msgid" - choose one which i think is close to my new feature request. Hello James, based on the "Specify thread msgid" message it looks like you were trying to request a feature using the Commitfest website? That won't work; the commitfest website is only intended as a tracker of in-progress development work. Without a Postgres code patch, that website doesn't help you any. What you have done amounts to hijacking an unrelated mailing list thread, which is discouraged and frowned upon. That said, sadly we don't have any official feature request system, Please start a new thread by composing an entirely new message to pgsql-hackers@lists.postgresql.org, and don't use the commitfest website for it. That said, > query: > > SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t1.a_indexed_col='some_value' OR t2.a_indexed_col='some_vable'; > > can the server automatically replace the OR logic above with UNION please? i.e. replace it with: > > (SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t1.a_indexed_col='some_value' ) > UNION > (SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t2.a_indexed_col='some_vable'); I have the feeling that this has already been discussed, but I can't find anything useful in the mailing list archives. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Saca el libro que tu religión considere como el indicado para encontrar la oración que traiga paz a tu alma. Luego rebootea el computador y ve si funciona" (Carlos Duclós)
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add missing index_insert_cleanup calls
- 41d2c6f952ed 17.0 landed
-
Fix a couple typos in BRIN code
- 95d14b7ae26d 17.0 landed
-
Check if ii_AmCache is NULL in aminsertcleanup
- a82ee7ef3aac 17.0 landed
-
Use fipshash in brin_multi test
- 86b64bafc19c 17.0 cited
-
Reuse BrinDesc and BrinRevmap in brininsert
- c1ec02be1d79 17.0 landed
-
Consider fillfactor when estimating relation size
- 29cf61ade3f2 17.0 cited
-
Postpone some stuff out of ExecInitModifyTable.
- c5b7ba4e67ae 14.0 cited