Re: shared buffers

I didnt know this. thanks, Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sat, Apr 26, 2025 at 12:46 AM Laurenz Albe wrote: > On Fri, 2025-04-25 at 15:42 +0200, Marc Millas wrote: > > got something strange to me: > > Same db ie. same data, around 1.2TB,one on pg

Re: shared buffers

Sorry, 'someone' launches some kind of batches without telling. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Fri, Apr 25, 2025 at 3:42 PM Marc Millas wrote: > hello, > > got something strange to me: > Same db ie. same data, around 1.2TB,one on pg13, on

replication

Hello, One of my customers tells me he did a replication with the master on a debian 10 and the slave on a debian 12, both with a pg13.20, one on a pgdg110+1, the other a pgdg120.1 is this a good idea ??? (I don't think so...) thanks, Marc MILLAS Senior Architect +33607850334

shared buffers

times I rerun the explain (analyze, buffers) of the same request, each time, the explain shows the same volume of reads. again and again. If I check with pg_buffercache, the set of objects stay the same, WITHOUT the objects of my request, just like if those objects where sticky. any idea ? thanks

Re: explain

Thanks ! Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Thu, Apr 24, 2025 at 3:41 PM David Rowley wrote: > On Fri, 25 Apr 2025 at 01:32, Marc Millas wrote: > > Nested Loop Left Join (cost=941400.77..966327.57 rows=3 width=653) > (actual time=52655.694..62533.811 ro

explain

=52655.694..62533.811 rows=346 loops=1) Buffers: shared hit=10068265 read=396705 dirtied=1858 written=218, temp read=429687 written=115187 I/O Timings: read=79368.246 write=11.486 So, the total execution time is 52655 ms ok and the total time for i/o is...79368 ms how ??? thanks Marc MILLAS Senior

psql meta command

Hello, on a customer postgres db, using psql, if I post \ to initiate, for exemple \x that psql immediately exits. somewhat boring as it blocks all psql meta commands. Is there a way to get the extended display without posting a \ ? thanks, Marc MILLAS Senior Architect +33607850334

Re: end of COPY

Greg... 👍 works fine now. thanks ! Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, Mar 5, 2025 at 4:53 PM Greg Sabino Mullane wrote: > On Wed, Mar 5, 2025 at 10:22 AM Marc Millas > wrote: > >> Then the flow contains a single line: \. to my understan

end of COPY

type numeric "\." then the 2 lines stating the copy command that was executed. what am I missing ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: old OS

👍👍👍 thanks Marc MILLAS Senior Architect +33607850334 On Tue, Feb 4, 2025 at 7:04 PM Tim Gerber wrote: > Appears PG 12 is available for RHEL 6 via the following repository: > > https://download.postgresql.org/pub/repos/yum/12/redhat/ > <https://download.postgresql.org/p

Re: old OS

l, as said, I will try to pipe data through the network, but this imply that data will be put exactly as psql, on the new machine, will be able to 'ingest' it. easy for most things, somewhat more boring for blobs... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, F

old OS

on a redhat 6.5 ? If nothing, I will try to pipe the data directly through the network connection, but this generates other problems. thanks for your help Marc MILLAS Senior Architect +33607850334

Re: Naive question about multithreading/multicore

Hello, On Sun, Oct 13, 2024 at 08:16:04AM +1300, Thomas Munro wrote: > > template1=> SELECT COUNT(*) FROM pg_class a, pg_class b, pg_class c; > > > > I see only one 100% CPU PostgreSQL process. > > If you set set min_parallel_table_scan_size = 0 then it uses Without it, it uses one CPU and takes

Naive question about multithreading/multicore

Hello, on a machine where starting two processes: perl -e 'while (1) { ; }' I see two processed at 100% CPU, which is expected (with top). Now, if I do: template1=> SELECT COUNT(*) FROM pg_class a, pg_class b, pg_class c; I see only one 100% CPU PostgreSQL process. I read that while Postgre

ldap fdw

from scratch ?!? what s your advice ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Partitioning options

by just getting rid of obsolete partitions which is quite speedy.( no delete, no vacuum, no index updates, ...) Marc > Keep in mind that SELECT queries being used on the partition must use the > partitioning KEY in the WHERE clause of the query or performance will > suffer. > >

Re: pg_dump/pg_restore --jobs practical limit?

Marc MILLAS Senior Architect +33607850334 www.mokadb.com Testing pg_restore with different --jobs= values will be easier. pg_dump > is what's going to be reading from a constantly varying system. > > Hello, > each time I do a replatforming of this kind, with DB up to 2 TB,

Re: event trigger clarification

Thanks ! Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, Aug 30, 2023 at 6:18 PM Erik Wienhold wrote: > > On 30/08/2023 17:12 CEST Marc Millas wrote: > > > > the doc v15 states: " pg_event_trigger_ddl_commands returns a list of DDL > > commands

Re: event trigger clarification

Thanks ! Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, Aug 30, 2023 at 8:44 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Wednesday, August 30, 2023, Marc Millas wrote: > >> Hi, >> the doc v15 states: " pg_event_trigger_ddl_c

event trigger clarification

s when the line is executed or at commit time. thanks. Marc MILLAS Senior Architect +33607850334 www.mokadb.com

shared buffers

ifferently, what could be advantages/disadvantages of such a setup ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: pb with big volumes

Hi David, that's exactly my question. does the analyze buffers data, generated when track_io_timing is on, keep track of multiple reloads of the same data while executing one operation ? I ll do the test asap and report the results. Marc MILLAS Senior Architect +33607850334 www.mokad

Re: pb with big volumes

s persistent volumes. > > What is the pipe connecting the database server to the disks? If it's > NAS, well that would explain it. > > HTH, > Adam > > > > On Thu, Aug 10, 2023 at 2:37 PM Marc Millas > wrote: > >> Hi, >> >> I have a 15 TB db

pb with big volumes

omplete data model and the exact requests can be considered mandatory, but when I change the request I get the very same behaviour... Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: DB Server slow down & hang during Peak hours of Usage

tgres 12: https://www.postgresql.org/docs/12/runtime-config-autovacuum.html Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, Aug 8, 2023 at 1:59 PM Marc Millas wrote: > Hello, > in the postgresql.conf joined, 2 things (at least) look strange: > 1) the values for b

Re: DB Server slow down & hang during Peak hours of Usage

try to set work_mem to 100 MB and check what's happening. Also check the logs, postgres tells his life there... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Mon, Aug 7, 2023 at 3:36 PM KK CHN wrote: > List , > > *Description:* > > Maintaining a DB Server

Re: suggestion about time based partitioning and hibernate

vue. and, obviously if you partition by id range, no pk pb. the difference is the SQL plan to access the data, as to prune partitions, Postgres need to have the partition key in the where clause. obviously, if your code do access the data thru id... then partition by id. > > Marc MILLAS > >

analyze partition

. If I run vacuum analyze ma_table on my big partitioned table (130+ partitions) it does work for quite a long time. Can someone clarify ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: need explanation about an explain plan

Le mer. 28 juin 2023 à 22:46, Laurenz Albe a écrit : > On Wed, 2023-06-28 at 19:25 +0200, Marc Millas wrote: > > Hi Laurenz, as said, in each partition there is only one value for > ladate. > > The planner doesn't seem to take that into account. > Indeed. I did check v

Re: need explanation about an explain plan

On Wed, Jun 28, 2023 at 6:48 PM Laurenz Albe wrote: > On Wed, 2023-06-28 at 17:29 +0200, Marc Millas wrote: > > https://explain.depesz.com/s/Opk0 > > > > The big table (10 billions raws) is split in around 130 partitions, one > by month. > > the ladate column is

Re: need explanation about an explain plan

, one column at a time (there are 107 columns...) I dont understand why the planner use a filter on the date, as its already within the partition structure. Thanks, Marc MILLAS On Wed, Jun 28, 2023 at 5:22 PM Marc Millas wrote: > Hi, > > Postgres 14.2 (for one more month) > The

need explanation about an explain plan

Hi, Postgres 14.2 (for one more month) The explain plan and request is here: https://explain.depesz.com/s/Opk0 The big table is split in around 130 partitions, one by month. the ladate column is the partition key, and it does have 1 value for each partition. there is a Marc MILLAS Senior

Re: pb with join plan

On Tue, Jun 27, 2023 at 8:12 PM Kirk Wolak wrote: > On Wed, Jun 21, 2023 at 12:10 PM Marc Millas > wrote: > >> Marc MILLAS >> On Wed, Jun 21, 2023 at 12:43 PM Tomas Vondra < >> tomas.von...@enterprisedb.com> wrote: >> >>> On 6/21/23 00:26, Mar

Re: bug or lacking doc hint

On Mon, Jun 26, 2023 at 4:05 PM Ron wrote: > On 6/26/23 07:22, Marc Millas wrote: > > > > On Mon, Jun 26, 2023 at 5:47 AM Avin Kavish wrote: > >> Sounds like the problem you are having is, the server is running out of >> temporary resources for the operation t

Re: bug or lacking doc hint

ng 3 merge join. And I have one more question: the explain analyze plan shows that Postgres decided to do external sorts using around 2 GB of disk space. I did a set work_mem to '4GB' to try to have those sorts in memory. No effect. How can I tell the planner to do those sort in memory ?? th

Re: bug or lacking doc hint

iting raw SQL queries, and I cannot let them write queries that are going to go on for ages, and eventually crash over temp_file_limit after hours every now and then. So, my understanding of the above is that I must inform the users NOT to use OR clauses into joins. which maybe a pb by itself. regards Marc > regards, tom lane > Marc MILLAS

Re: bug or lacking doc hint

On Sun, Jun 25, 2023 at 9:35 PM David Rowley wrote: > On Mon, 26 Jun 2023 at 03:02, Marc Millas wrote: > > When I ask this list, David Rowley suggest to rewrite the SQL, replacing > the OR by a union. > > > > Fine, this do work, even if a bit complex as the original SQL

bug or lacking doc hint

syntax as soon as there is some data volumes. So, now I am writing some kind of recipe book for the users of that DB. What should I write ? Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: pb with join plan

Marc MILLAS On Wed, Jun 21, 2023 at 12:43 PM Tomas Vondra wrote: > On 6/21/23 00:26, Marc Millas wrote: > > > > > > On Tue, Jun 20, 2023 at 11:19 PM David Rowley > <mailto:dgrowle...@gmail.com>> wrote: > > > > On Wed, 21 Jun 2023

Re: pb with join plan

On Wed, Jun 21, 2023 at 12:43 PM Tomas Vondra wrote: > On 6/21/23 00:26, Marc Millas wrote: > > > > > > On Tue, Jun 20, 2023 at 11:19 PM David Rowley > <mailto:dgrowle...@gmail.com>> wrote: > > > > On Wed, 21 Jun 2023 at 08:34, Marc Millas

Re: pb with join plan

On Tue, Jun 20, 2023 at 11:19 PM David Rowley wrote: > On Wed, 21 Jun 2023 at 08:34, Marc Millas wrote: > > > > On Tue, Jun 20, 2023 at 10:14 PM David Rowley > wrote: > >> > >> On Wed, 21 Jun 2023 at 07:42, Marc Millas > wrote: > >> > But i

Re: pb with join plan

On Tue, Jun 20, 2023 at 10:14 PM David Rowley wrote: > On Wed, 21 Jun 2023 at 07:42, Marc Millas wrote: > > But if I do the same with clause one OR clause 2, I have to kill the > request after an hour, seeing the filesystem showing more than 140 Mb of > increased usage. &

pb with join plan

been vacuum analyzed. thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: date format

On Wed, Jun 14, 2023 at 8:23 PM Marc Millas wrote: > > > > > On Wed, Jun 14, 2023 at 8:15 PM Ron wrote: > >> On 6/14/23 13:02, Marc Millas wrote: >> >> >> On Wed, Jun 14, 2023 at 7:27 PM David G. Johnston < >> david.g.johns...@gmail.com> wro

Re: date format

On Wed, Jun 14, 2023 at 8:15 PM Ron wrote: > On 6/14/23 13:02, Marc Millas wrote: > > > On Wed, Jun 14, 2023 at 7:27 PM David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Wed, Jun 14, 2023 at 9:42 AM Marc Millas >> wrote: >> >>>

Re: date format

On Wed, Jun 14, 2023 at 7:27 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Wed, Jun 14, 2023 at 9:42 AM Marc Millas > wrote: > >> Hi, >> >> I would like to load data from a file via file_fdw or COPY.. its a >> postgres 14 cluster >

date format

load as char and then apply an appropriate transformation. no pb. But is there a direct way to do this ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Hash Index on Partitioned Table

y' parameter in create index doc). doing this it was easy to somewhat optimize the process according to number of available core/RAM/storage. hf Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, May 31, 2023 at 7:53 PM peter.boris...@kartographia.com < peter.boris...@

Re: syntax pb

Thanks for the explanation. Crystal clear, thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, May 30, 2023 at 7:31 PM Tom Lane wrote: > "David G. Johnston" writes: > > On Tue, May 30, 2023 at 8:53 AM Marc Millas > wrote > >> Too my

Re: syntax pb

Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, May 30, 2023 at 7:12 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Tue, May 30, 2023 at 8:53 AM Marc Millas wrote > > >> This comes from a prod environment and even casting NULLs (which is

Re: syntax pb

Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, May 30, 2023 at 3:51 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Tuesday, May 30, 2023, Marc Millas wrote: > >> >> I get: >> ERROR: column "d" is of type numeric

Re: syntax pb

ge, BTW) generates absurd errors. Too my understanding it looks like the parser did not parse the select distinct as we think he does. > >> Marc MILLAS > >> Senior Architect > >> +33607850334 > >> www.mokadb.com <http://www.mokadb.com> > >> > > > > -- > Adrian Klaver > adrian.kla...@aklaver.com > >

syntax pb

of type numeric but expression is of type text LINE 2: Select distinct test1.t, 'abc' as b, NULL as c, NULL as d HINT: You will need to rewrite or cast the expression. Can someone give a short SQL syntax hint ? thanks, Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?

Hi Thomas, to my understanding, there is ONE master key for TDE in 12c. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sun, May 21, 2023 at 9:47 PM Thomas Kellerer wrote: > > Marc Millas schrieb am 21.05.2023 um 13:13: > > Oracle have One (1) DB per instance (in Or

Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?

?? the sqlite thing ?? Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sun, May 21, 2023 at 7:15 PM Theodore M Rolle, Jr. wrote: > What about sqlcipher? > > On Sun, May 21, 2023, 07:16 Marc Millas wrote: > >> Oracle have One (1) DB per instance (in Oracle its n

Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?

Oracle have One (1) DB per instance (in Oracle its not named a cluster as...there is only one !). So ... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Thu, May 18, 2023 at 9:30 PM Adrian Klaver wrote: > On 5/18/23 11:56, Ron wrote: > > On 5/18/23 12:54, Rob Sarg

Re: order by

On Thu, May 11, 2023 at 11:08 PM Ron wrote: > On 5/11/23 09:55, Marc Millas wrote: > > Thanks, > > I do know about index options. > > that table have NO (zero) indexes. > > > If the table has no indices, then why did you write "it looks like there > is

Re: Death postgres

On Fri, May 12, 2023 at 8:31 AM Peter J. Holzer wrote: > On 2023-05-11 21:27:57 +0200, Marc Millas wrote: > > the 75 lines in each tables are not NULLs but '' empty varchar, > which, > > obviously is not the same thing. > > and which perfectly generates 50

Re: Death postgres

On Thu, May 11, 2023 at 1:56 AM Peter J. Holzer wrote: > On 2023-05-10 22:52:47 +0200, Marc Millas wrote: > > On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer > wrote: > > > > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > > Unique (cost=723

Re: gather merge

so, I put max_parallel_workers_per_gather to 0, and it does work, no more parallel execution. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Thu, May 11, 2023 at 4:38 PM Marc Millas wrote: > Hi, > > another new thread related to "death postgres": > how to

Re: order by

On Thu, May 11, 2023 at 5:23 PM Adrian Klaver wrote: > On 5/11/23 08:00, Marc Millas wrote: > > > > On Thu, May 11, 2023 at 4:43 PM Adrian Klaver > <mailto:adrian.kla...@aklaver.com>> wrote: > > > > On 5/11/23 07:29, Marc Millas wrote: > &g

Re: order by

On Thu, May 11, 2023 at 4:43 PM Adrian Klaver wrote: > On 5/11/23 07:29, Marc Millas wrote: > > Hi, > > > > I keep on investigating on the "death postgres" subject > > but open a new thread as I don't know if it's related to my pb. > > >

Re: order by

Thanks, I do know about index options. that table have NO (zero) indexes. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Thu, May 11, 2023 at 4:48 PM Adam Scott wrote: > Check the index creation has NULLS FIRST (or LAST) on both indexes that > are used. Use explain to se

gather merge

Hi, another new thread related to "death postgres": how to stop Gather Merge from going parallel ? ie. not forcing parallel to one thread as limitating max_parallel_workers (per_gatherer) thanks, Marc MILLAS Senior Architect +33607850334 www.mokadb.com

order by

archar (?!?) between those 2 clusters. What can I check to to explain this difference as, to my understanding, it's not a postgresql.conf parameter. thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Death postgres

On Thu, May 11, 2023 at 1:56 AM Peter J. Holzer wrote: > On 2023-05-10 22:52:47 +0200, Marc Millas wrote: > > On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer > wrote: > > > > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > > Unique (cost=723

Re: Death postgres

On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer wrote: > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > Unique (cost=72377463163.02..201012533981.80 rows=1021522829864 > width=97) > >-> Gather Merge (cost=72377463163.02..195904919832.48 > row

Re: Death postgres

On Sun, May 7, 2023 at 8:42 PM Laurenz Albe wrote: > On Sat, 2023-05-06 at 03:14 +0200, Marc Millas wrote: > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom kill

Re: Death postgres

Le sam. 6 mai 2023 à 21:46, Adrian Klaver a écrit : > On 5/6/23 10:13, Marc Millas wrote: > > > > > > > When you restarted the server where there any warnings shown? > > > > Sadly, I cannot. Will be done next tuesday. > > Cannot do what: > >

Re: Death postgres

Le sam. 6 mai 2023 à 18:11, Adrian Klaver a écrit : > On 5/6/23 05:25, Marc Millas wrote: > > > > > > Le sam. 6 mai 2023 à 06:18, Adrian Klaver > <mailto:adrian.kla...@aklaver.com>> a écrit : > > > > On 5/5/23 18:14, Marc Millas wrote: > >

Re: Death postgres

Le sam. 6 mai 2023 à 15:15, Ron a écrit : > On 5/6/23 07:19, Marc Millas wrote: > > > > Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > >> On 2023-05-06 03:14:20 +0200, Marc Millas wrote: >> > postgres 14.2 on Linux redhat >> > >> > te

Re: Death postgres

Le sam. 6 mai 2023 à 15:15, Ron a écrit : > On 5/6/23 07:19, Marc Millas wrote: > > > > Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > >> On 2023-05-06 03:14:20 +0200, Marc Millas wrote: >> > postgres 14.2 on Linux redhat >> > >> > te

Re: Death postgres

Le sam. 6 mai 2023 à 06:18, Adrian Klaver a écrit : > On 5/5/23 18:14, Marc Millas wrote: > > Hi, > > > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom k

Re: Death postgres

Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > On 2023-05-06 03:14:20 +0200, Marc Millas wrote: > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom kill

Death postgres

, Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: missing something about json syntax

Ok, thanks. Le jeu. 20 avr. 2023 à 22:42, Tom Lane a écrit : > Marc Millas writes: > > but it doesnt explain how postgres is able to put a scalar in a json or > > jsonb column without pb: > > I don't understand how this ('"{\"t\"}"') can

Re: missing something about json syntax

can be considered a valid enough json to be inserted in a json column and at the same time invalid for all other json uses. just like if postgres was allowing to insert things that are not of the column type it's the first time I do encounter this kind of behaviour from postgres Marc MILLAS

missing something about json syntax

l' from mytable, or select _data->'level' from anothertable sure if I look at the json field one is showed { "tag": "value", ... and the other is showed "{\"tag\":\"value\", ... not the very same so 2 questions: 1) how postgres can feed a json or jsonb column and CANNOT use the values in it ?? 2) how to "transform" the inappropriate json into a usable one ? of course, if what I am missing is very obvious, I apologize... Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: SIze 0 in pg_stat_file, pg_stat_progress_copy

Sorry... someone did setup the log as a named pipe... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Fri, Apr 14, 2023 at 4:26 PM Marc Millas wrote: > Hi, > > on a debian machine, with a postgres 14,2 server > > logs in a dedicated directory (not log) > when l

SIze 0 in pg_stat_file, pg_stat_progress_copy

files --and when running a copy from the current logfile with a where clause to choose only the current day logs, the bytes total column is 0 what can provides such a behaviour ? thanks, Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Oracle to PostgreSQL Migration

EDB do have a replication server which can be used to transfer real time data from oracle to postgres. don't know if it can be used to get to "no downtime" BTW what do you call "no downtime" as anyway a switch, as fast as it can be do take ""some"

Re: pg_reload_conf()

Thanks Adrian, the fact that the changes are visible only by the new backend, and NOT by the backend which did the changes was what I did missed. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Mon, Feb 20, 2023 at 6:01 PM Adrian Klaver wrote: > On 2/20/23 08:57, Marc Mil

pg_reload_conf()

sly, if I stop and restart the DB, select setting, boot_val, reset_val from pg_settings where name='log_connections'; on off on So, I am perplexed: what pg_reload_conf() is doing/not doing ? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?

hings, one may get stupid results...it was an "expert only" functionality :-) Still, in some cases, it was very useful to manage the rare cases where the planner cannot, for whatever reason do a good job. OK its not the way postgres do behave. Still, in some cases... Marc M

Re: Best Open Source OS for Postgresql

the whole thing with all associated libs ... Thanks Which was my customer requirelent Le mar. 31 janv. 2023 à 17:38, Adrian Klaver a écrit : > On 1/31/23 05:09, Marc Millas wrote: > > Sorry for inappropriate "reply". > > > > if you do check the debian postgis

Re: Best Open Source OS for Postgresql

Hello, What about postgis : 3.0, 3.3, 3.4 ?? Le mer. 1 févr. 2023 à 07:20, Tony Shelver a écrit : > > Copied to the list > On Wed, 1 Feb 2023 at 08:18, Tony Shelver wrote: > >> >> >> On Wed, 1 Feb 2023 at 08:04, Tony Shelver wrote: >> >>>

Re: Best Open Source OS for Postgresql

all cross possibilities (ie. 5 postgres x 6 postgis, less some impossibilities according to postgis matrix) so... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Tue, Jan 31, 2023 at 1:23 PM hubert depesz lubaczewski wrote: > On Tue, Jan 31, 2023 at 01:18:08PM +0100, Marc Millas w

Re: alter table impact on view

A bit sad Thanks.. Le lun. 30 janv. 2023 à 13:53, David Rowley a écrit : > On Tue, 31 Jan 2023 at 01:14, Marc Millas wrote: > > But if I alter table to change a column that is a varchar 20 into a > varchar 21 > > postgres refuse saying that it cannot due to the return ru

alter table impact on view

lighten me? thanks, Marc MILLAS Senior Architect +33607850334 www.mokadb.com

Re: Autovacuum on sys tables

This is a test. Apologies but 19/12 we are no longer receiving the list mails

Re: impact join syntax ?? and gist index ??

I read your answer, Tom, but I cannot connect it to my measurements: why adding the index did slow the request twice ?? Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sat, Jan 7, 2023 at 10:33 PM Tom Lane wrote: > Marc Millas writes: > > 2023=# explain (analyze, buffer

Re: impact join syntax ?? and gist index ??

Index Cond: (geom ~ B.geom) Filter: st_within(B.geom, geom) Rows Removed by Filter: 0 Buffers: shared hit=2112857 Planning Time: 0.252 ms Execution Time: 11863.357 ms (26 lignes) Marc MILLAS Senior Architect +3360785033

Re: impact join syntax ?? and gist index ??

discussion about the versions my project will use :-) Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sat, Jan 7, 2023 at 8:46 PM Marc Millas wrote: > Hi, > > postgres 12, postgis 3.0 > > I have a small table A, 11 rows with a varchar column x and a geometry >

Re: impact join syntax ?? and gist index ??

Yes, I know the 2 syntax provide a different result: one provides the 6 meaningful lines, the left join do add 5 lines with a count of 0... ... Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Sat, Jan 7, 2023 at 8:46 PM Marc Millas wrote: > Hi, > > postgres 12, postgis

impact join syntax ?? and gist index ??

missing something.. (at least 2 things...) can someone shed some light ?? thanks Marc MILLAS Senior Architect +33607850334 www.mokadb.com

pgBackRest on MacOS

Has anybody pgbackrest running on MacOS ( Monterey ? ) If yes are you willing to share the how to ? Or can anybody guide us to an “easy” how to ? Many thanks in advance, Marc

limits, indexes, views and query planner

to exclude the table_b earlier in its plan and to possibly fallback to a plan equivalent to the first one. with a view on a single table (test_av), the index is used. An oddity in the plan is the expected row count in "Append"(11) ... ( tested on postgres 14 ) Regards, Marc Mami

Re: postgis

right. so I scratch the debian vm, install a centos 7 and within minutes I have a postgres 12 with postgis 3.0.4 running. so easy. regards. Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, Jul 20, 2022 at 7:27 PM Imre Samu wrote: > > I would expect the 35 packages impl

Re: postgis

Thanks for your answer. I would like to avoid compiling as much as possible. I know that postgis 3.2.1 is available and does install without pb. but.. That db run an app which is very long to test, so I need to stick to a postgis 3.0.x regards, Marc MILLAS Senior Architect +33607850334

Re: postgis

nfo on the debian postgis page I was able to find is the name of a package: postgres-12-postgis-3 which do install a postgis 3.2.1 not a postgis 3.0.x Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Wed, Jul 20, 2022 at 3:52 PM Ron wrote: > This long drama is about *

  1   2   >