Re: Recommendation to run vacuum FULL in parallel

Perumal Raj wrote: > We are planning to reclaim unused space from 9.2 Version postgres Cluster, > > Method : VACUUM FULL > DB Size : 500 GB > Expected space to reclaim 150 GB > work_mem : 250 MB > maintenance_work_mem : 20 GB > > Question : > > 1. vacuumdb --j option (Parallel) not available fo

Re: Recommendation to run vacuum FULL in parallel

On 4/3/19 12:50 AM, Perumal Raj wrote: Hi ALL We are  planning to reclaim unused space from 9.2 Version postgres Cluster, Method : VACUUM FULL Does *every* table have *so much* free space that it's impractical to just let the files just get refilled by normal usage? DB Size : 500 GB Expec

Recommendation to run vacuum FULL in parallel

Hi ALL We are planning to reclaim unused space from 9.2 Version postgres Cluster, Method : VACUUM FULL DB Size : 500 GB Expected space to reclaim 150 GB work_mem : 250 MB maintenance_work_mem : 20 GB *Question :* 1. vacuumdb --j option (Parallel) not available for version 9.2. How to run vac

Re: New LLVM JIT Features

On 2019-04-03 10:44:06 +0530, preejackie wrote: > Hi Andres, > > Thanks for the reply! Please see my comments inline. > > On 03/04/19 3:20 AM, Andres Freund wrote: > > Hi, > > > > On 2019-04-02 00:51:51 +0530, preejackie wrote: > > > As LLVM ORC supports compiling in multiple backend threads, it

Re: New LLVM JIT Features

Hi Andres, Thanks for the reply! Please see my comments inline. On 03/04/19 3:20 AM, Andres Freund wrote: Hi, On 2019-04-02 00:51:51 +0530, preejackie wrote: As LLVM ORC supports compiling in multiple backend threads, it would be effective if we compile the functions speculatively before they

Re: template0 is having high age of datforzenxid

Hi, On 2019-04-02 15:35:53 -0700, AI Rumman wrote: > I am running Postgresql 10 where I can see the template0 database is having > longest datfrozenxid: > ```db_name age_of_datfrozenxid > -- > postgres251365 > template1234574 > template075366462 > d

template0 is having high age of datforzenxid

Hi, I am running Postgresql 10 where I can see the template0 database is having longest datfrozenxid: ```db_name age_of_datfrozenxid -- postgres251365 template1234574 template075366462 db1253097 db2250649 db3250649 db414641 db514

Re: New LLVM JIT Features

Hi, On 2019-04-02 00:51:51 +0530, preejackie wrote: > As LLVM ORC supports compiling in multiple backend threads, it would be > effective if we compile the functions speculatively before they are called > by the executing function. So when we request JIT to compile a function, JIT > will immediate

Re: New LLVM JIT Features

On Wed, Apr 3, 2019 at 8:39 AM Praveen Velliengiri wrote: > On Apr 2, 2019 12:51 AM, "preejackie" wrote: >> I'm Praveen Velliengiri, student from India. I'm working on developing a >> Speculative compilation support in LLVM ORC JIT Infrastructure. >> >> As LLVM ORC supports compiling in multiple

Re: max_prepared_foreign_transactions is unrecognized

On 4/2/19 1:02 PM, Eric J. Van der Velden wrote: Please reply to list also. Ccing list Hi. Thanks. In fact my question is if postgres has software by which I can do distributed transactions, with 2pc. Normally I use narayana in wildfly for that, but has postgres also such software? In java they

Re: Running psql in emacs shell generates key conflict error: why? [FIXED]

On Tue, 2 Apr 2019, Adrian Klaver wrote: What was the exact message? What was in the last line? Difference in shell escaping? Adrian, Cannot answer the first two because that work is long gone. So, I just tried it again with only one row to insert and psql inserted that row without complaint.

Re: Running psql in emacs shell generates key conflict error: why?

On 4/2/19 8:00 AM, Rich Shepard wrote: An unexpected result this morning that I'd like to understand. In emacs I loaded the file organizations.sql in a buffer to insert new rows in that table. Rather than running psql from a virtual console, I opened an emacs shell and entered the command,   psq

Re: max_prepared_foreign_transactions is unrecognized

On 4/2/19 12:36 PM, Eric J. Van der Velden wrote: On https://wiki.postgresql.org/wiki/2PC_on_FDW it says I have to set the configuration parameter "max_prepared_foreign_transactions"  in postgresql.conf. When I restart postgres, I see: From what I see the above was a proposal that did not actu

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

On Mon, Apr 1, 2019 at 4:04 PM Jonathan S. Katz wrote: > > > On Apr 1, 2019, at 9:55 AM, Tom Lane wrote: > > > > Magnus Hagander writes: > >>> On Sat, Mar 30, 2019 at 10:16 PM Tom Lane wrote: > >>> Yeah; this is supposing that there is a security boundary between > >>> Postgres superusers and

Re: New LLVM JIT Features

hi I'm following up on this request, please feel free to reply On Apr 2, 2019 12:51 AM, "preejackie" wrote: > Hi > > I'm Praveen Velliengiri, student from India. I'm working on developing a > Speculative compilation support in LLVM ORC JIT Infrastructure. > > As LLVM ORC supports compiling in mu

max_prepared_foreign_transactions is unrecognized

On https://wiki.postgresql.org/wiki/2PC_on_FDW it says I have to set the configuration parameter "max_prepared_foreign_transactions" in postgresql.conf. When I restart postgres, I see: LOG: unrecognized configuration parameter "max_prepared_foreign_transactions" in file "/var/lib/postgresql/data

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

On 4/2/19 2:08 PM, Magnus Hagander wrote: > On Tue, Apr 2, 2019 at 5:31 PM Andres Freund > wrote: > > Hi, > > On 2019-04-02 07:35:02 -0500, Brad Nicholson wrote: > > Michael Paquier mailto:mich...@paquier.xyz>> > wrote on 04/02/2019 01:05:01 AM: > >

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

On Tue, Apr 2, 2019 at 5:31 PM Andres Freund wrote: > Hi, > > On 2019-04-02 07:35:02 -0500, Brad Nicholson wrote: > > Michael Paquier wrote on 04/02/2019 01:05:01 AM: > > > > > From: Michael Paquier > > > To: "Jonathan S. Katz" > > > Cc: Tom Lane , Magnus Hagander > > > , Daniel Verite , > > >

Re: [SPAM] Re: Key encryption and relational integrity

Il 01/04/2019 20:48, Rory Campbell-Lange ha scritto: On 01/04/19, Moreno Andreo (moreno.and...@evolu-s.it) wrote: ... I'm not forced to use pseudonimysation if there's the risk to get things worse in a system. I've got to speak about these"two opposing forces at work" to a privacy expert (maybe

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

Hi, On 2019-04-02 07:35:02 -0500, Brad Nicholson wrote: > Michael Paquier wrote on 04/02/2019 01:05:01 AM: > > > From: Michael Paquier > > To: "Jonathan S. Katz" > > Cc: Tom Lane , Magnus Hagander > > , Daniel Verite , > > pgsql-general > > Date: 04/02/2019 01:05 AM > > Subject: Re: CVE-2019-

Re: logical replication - negative bitmapset member not allowed

On 02/04/2019 15:46, Tom Lane wrote: > I'm glad you're out of the woods, but we still have a bug there > waiting to bite the next person. I wonder if you'd be willing to > spend some time trying to develop a reproduction sequence for this > (obviously, working on a test setup not your live servers

Running psql in emacs shell generates key conflict error: why?

An unexpected result this morning that I'd like to understand. In emacs I loaded the file organizations.sql in a buffer to insert new rows in that table. Rather than running psql from a virtual console, I opened an emacs shell and entered the command, psql -f organizations.sql -d bustrac and saw

Re: logical replication - negative bitmapset member not allowed

Tim Clarke writes: > I've cleared it by dropping the slave database, re-creating from the > live schema then fully replicating. Its all running happily now. I'm glad you're out of the woods, but we still have a bug there waiting to bite the next person. I wonder if you'd be willing to spend some

Re: Fwd: Postgresql with nextcloud in Windows Server

On 4/1/19 10:03 PM, 김준형 wrote: 보낸사람: *김준형* mailto:wnsuddl...@gmail.com>> Date: 2019년 4월 2일 (화) 오후 2:02 Subject: Re: Postgresql with nextcloud in Windows Server To: Adrian Klaver > Thanks for your reply and I hope this answers can help your questions 1) The n

Re: logical replication - negative bitmapset member not allowed

On 02/04/2019 14:59, Tom Lane wrote: > Well, that's not much help :-(. Can you provide any info to narrow > down where this is happening? I mean, you haven't even told us whether > it's the primary or the slave that is complaining. Does it seem to > be associated with any particular command? (T

Re: logical replication - negative bitmapset member not allowed

Tim Clarke writes: > Dang. I just replicated ~380 tables. One was missing an index so I > paused replication, added a unique key on publisher and subscriber, > re-enabled replication and refreshed the subscription. Well, that's not much help :-(. Can you provide any info to narrow down where thi

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

On 4/2/19 1:05 AM, Michael Paquier wrote: > On Mon, Apr 01, 2019 at 10:04:32AM -0400, Jonathan S. Katz wrote: >> +1, though I’d want to see if people get noisier about it before we rule >> out an official response. >> >> A blog post from a reputable author who can speak to security should >> be goo

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

Michael Paquier wrote on 04/02/2019 01:05:01 AM: > From: Michael Paquier > To: "Jonathan S. Katz" > Cc: Tom Lane , Magnus Hagander > , Daniel Verite , > pgsql-general > Date: 04/02/2019 01:05 AM > Subject: Re: CVE-2019-9193 about COPY FROM/TO PROGRAM > > On Mon, Apr 01, 2019 at 10:04:32AM -040

Re: WAL Archive Cleanup?

That seems to be a misconfigured client application that explicitly tries to connect to a non-existent database 'admin' (via db=admin). Instead of adding that database, it seems more logical to fix the client configuration. On Tue, 2 Apr 2019 at 09:53, Foo Bar wrote: > Hello All, > > Ok, so mayb

Re: WAL Archive Cleanup?

Hello All, Ok, so maybe something helpful? On my master node I am seeing a bunch of: 2019-03-28 23:54:44 GMT [2611]: [1-1] user=admin,db=admin,client=17210.10.37 172.10.10.37(57552) (0:3D000)FATAL: database "admin" does not exist 2019-03-28 23:54:46 GMT [2613]: [1-1] user=admin,db=admin,client=1

Re: WAL Archive Cleanup?

Hello All, Ok, so creating the admin database has not enabled my cluster to cleanup the `archive/` directory... It did eliminate the errors, though I'm dubious as to if that was the correct solution... Everything I'm able to google talks about setting up archive replication, but not how to keep

Re: WAL Archive Cleanup?

Hello All, Ok, I think maybe I've been approaching this all wrong. According to THIS SO post: "PostgreSQL doesn't manage the archive directory for you, that is up to you. It doesn't even know where (or what) the archive location is, that is why it asks you

Re: logical replication - negative bitmapset member not allowed

Dang. I just replicated ~380 tables. One was missing an index so I paused replication, added a unique key on publisher and subscriber, re-enabled replication and refreshed the subscription. The table has only 7 columns, I added a primary key with a default value from a new sequence. Tim Clarke IT