On 21.01.2020 0:00, Darafei "Komяpa" Praliaskouski wrote:
Hi,
Found out today that BRIN indexes don't really work for PostGIS and
box datatypes.
Since
https://github.com/postgres/postgres/commit/7e534adcdc70866e7be74d626b0ed067c890a251 Postgres
requires datatype to provide correlation stati
On 20.03.2023 22:27, Gregory Stark (as CFM) wrote:
On Sun, 22 Jan 2023 at 18:22, Tomas Vondra
wrote:
I wonder if we have other functions doing something similar, i.e.
accepting a polymorphic type and then imposing additional restrictions
on it.
Meh, there's things like array comparison functio
On 24.03.2023 01:46, Tomas Vondra wrote:
So if you could clean it up a bit, and do something about the two open
items I mentioned (a bunch of tests on different array,
I've added some tests to resgress/sql/rangetypes.sql, based on the same
dataset that is used to test lower() and upper().
Hi Alexander,
On 25.11.2023 02:06, Alexander Korotkov wrote:
In conclusion of all of the above, I decided to revise the patch and
show the bounds histogram as it's stored in pg_statistic. I revised
the docs correspondingly.
So basically we returned to what it all has started from? I guess i
oncurrency' GUC directly,
should call get_tablespace_maintenance_io_concurrency().
Ah, yeah, of course.
Updated patch attached.
I happened to notice that get_tablespace_io_concurrency() is called
instead of get_tablespace_maintenance_io_concurrency(). It doesn't look
right, no?
Regards,
Egor Rogov.
Hi Tomas,
On 21.01.2023 00:50, Tomas Vondra wrote:
Hi Egor,
While reviewing a patch improving join estimates for ranges [1] I
realized we don't show stats for ranges in pg_stats, and I recalled we
had this patch.
I rebased the v2, and I decided to took a stab at showing separate
histograms for
Hi,
On 23.01.2023 02:21, Tomas Vondra wrote:
On 1/22/23 22:33, Justin Pryzby wrote:
On Sun, Jan 22, 2023 at 07:19:41PM +0100, Tomas Vondra wrote:
On 1/21/23 19:53, Egor Rogov wrote:
Hi Tomas,
On 21.01.2023 00:50, Tomas Vondra wrote:
This simply adds two functions, accepting/producing
On 23.01.2023 13:01, Egor Rogov wrote:
On 23.01.2023 02:21, Tomas Vondra wrote:
On 1/22/23 22:33, Justin Pryzby wrote:
On Sun, Jan 22, 2023 at 07:19:41PM +0100, Tomas Vondra wrote:
On 1/21/23 19:53, Egor Rogov wrote:
Hi Tomas,
On 21.01.2023 00:50, Tomas Vondra wrote:
This simply adds two
,"[1,11)","[2,12)","[3,13)","[4,14)","[5,15)","[6,16)","[7,17)","[8,18)","[9,19)","[10,20)"}
Regards,
Egor Rogov.
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index f517a7d4a
Hi,
thanks for the review and corrections.
On 11.07.2021 21:54, Soumyadeep Chakraborty wrote:
Hello,
This should have been added with [1].
Excerpt from the documentation:
"pg_stats is also designed to present the information in a more readable
format than the underlying catalog — at the cost
Hi Tomas,
On 12.07.2021 16:04, Tomas Vondra wrote:
On 7/12/21 1:10 PM, Egor Rogov wrote:
Hi,
thanks for the review and corrections.
On 11.07.2021 21:54, Soumyadeep Chakraborty wrote:
Hello,
This should have been added with [1].
Excerpt from the documentation:
"pg_stats is also design
Hello everybody,
On 12.06.2024 20:13, Igor V.Gnatyuk wrote:
Hello.
Before the advent of procedures in PostgreSQL 11 that can manage
transactions, there could only be one transaction
in one statement. Hence the end of the transaction also meant the end
of the statement. Apparently, this is why
stat_statements).
--
Egor Rogov
Postgres Professional http://www.postgrespro.com
Hi,
I wonder if there is some hidden logic behind exposing (or not exposing)
index AM properties at SQL level?
For example, should newly added amcanbuildparallel (b437571) be
available via pg_indexam_has_property()? And also other boolean
properties like ampredlocks or amusemaintenanceworkme
14 matches
Mail list logo
