On 11/09/2025 16:11, Peter Eisentraut wrote:
Here is a patch for that. Please test it against your setup.
Thanks a lot. Here is a test, and IMHO, it looks good.
-- version 1 of monextension is in /tmp/extensions/share/extension
postgres=# show extension_control_path ;
extensi
On 11/09/2025 20:03, Pierrick wrote:
-- make a mistake in first folder
postgres=# alter system set extension_control_path =
'$system:/tmp/extension_old/share:/tmp/extensions/share';
ALTER SYSTEM
postgres=# select pg_reload_conf();
pg_reload_conf
t
(1 ligne)
On 09/09/2025 16:18, Matheus Alcantara wrote:
On Tue Sep 9, 2025 at 4:53 AM -03, Pierrick wrote:
On 08/09/2025 17:35, Tom Lane wrote:
"David G. Johnston" writes:
On Monday, September 8, 2025, Matheus Alcantara
wrote:
On this step it will search the .control
file o
On 08/09/2025 17:35, Tom Lane wrote:
"David G. Johnston" writes:
On Monday, September 8, 2025, Matheus Alcantara
wrote:
On this step it will search the .control
file on paths at extension_control_path in order and it will use the
first one that it finds and based on the .control file found
--+---
monextension | 2.0 | 2.0 | Meilleure
monextension | 1.0 | 2.0 | Mon extension
Don't you think that the command
create extension monextension version "1.0" ;
should be accepted by checking in all paths ?
Pierrick,
Hello,
Thanks a lot for your clear answer.
On 16/07/2024 19:54, Tomas Vondra wrote:
On 7/16/24 17:43, Pierrick Chovelon wrote:
...
Quite fast as well...
Have you got an idea on the initial issue ? Why when using a prepared
statement and a gin index the execution time "explode" ?
Hello,
One of our customer is facing an issue regarding a prepared statement
and a gin index.
An important gap between execution times can be shown when using execute
or plain literals.
Here is the test that shown this issue :
Init table :
create table tmp_tk_test_index
(
sync_id
