Re: [GENERAL] What is the best thing to do with PUBLIC schema in Postgresql database

- Original Message - > From: "Patricia Hu" > Sent: Friday, November 4, 2016 9:58:10 AM > > Since it could potentially be a security loop hole. So far the action taken > to address it falls into these two categories: > > drop the PUBLIC schema altogether. ...

Re: [GENERAL] CachedPlan logs until full disk

Job writes: > it is the second time (in two weeks), that have a very strange Postgresql in > a 8.4.22 installation (32 bit still). You realize, of course, that 8.4.x has been out of support for a couple of years now. > Logfile grow up (in few hours) until filling

[GENERAL] CachedPlan logs until full disk

Hello guys, it is the second time (in two weeks), that have a very strange Postgresql in a 8.4.22 installation (32 bit still). Logfile grow up (in few hours) until filling the Whole disk space. I can read infinite series of this messages: CachedPlan: 1024 total in 1 blocks; 640 free (0

Re: [GENERAL] replication setup: advice needed

> You need to look at a replication solution like Slony, which is a trigger > based replication solution. If you are using PostgreSQL version 9.4 or > higher, then, you can explore "pglogical" which is WAL based and uses > logical decoding capability. I'm using 9.4, and I'm looking at pglogical

Re: [GENERAL] What is the best thing to do with PUBLIC schema in Postgresql database

On 11/4/16 3:58 PM, Hu, Patricia wrote: Since it could potentially be a security loop hole. So far the action taken to address it falls into these two categories: drop the PUBLIC schema altogether. One of the concerns is with some of the system objects that have been exposed through

Re: [GENERAL] Recover from corrupted database due to failing disk

On 4 November 2016 at 11:20, Gionatan Danti wrote: > Unfortuntaly I am working with incredible constrains from customer side; > even buying two SAS disks seems a problem. Moreover, as an external > consultant, I have basically no decision/buying power :| > What I can do (and I

Re: [GENERAL] How to hint 2 coulms IS NOT DISTINCT FROM each other

On 4 November 2016 at 14:41, Merlin Moncure wrote: > On Fri, Nov 4, 2016 at 8:08 AM, Kim Rose Carlsen wrote: >> The nulls are generated by something like this >> SELECT c.circuit_id, >>cc.customer_id >>FROM circuit AS c >> LEFT

Re: [GENERAL] Recover from corrupted database due to failing disk

On 11/04/2016 03:20 AM, Gionatan Danti wrote: On 03/11/2016 14:20, Adrian Klaver wrote: The above does not make sense. You are having to recover because there was no backup and now you want to go forward without doing a backup? Hi Adrian, no, I don't want go forward without backups ;)

[GENERAL] What is the best thing to do with PUBLIC schema in Postgresql database

Since it could potentially be a security loop hole. So far the action taken to address it falls into these two categories: drop the PUBLIC schema altogether. One of the concerns is with some of the system objects that have been exposed through PUBLIC schema previously, now they will need

Re: [GENERAL] How to hint 2 coulms IS NOT DISTINCT FROM each other

On Fri, Nov 4, 2016 at 8:08 AM, Kim Rose Carlsen wrote: >>> It might raise another problem, that the nulls are generated through LEFT > >>> JOINS where no rows are defined. Then the 0 or -1 value need to be >>> a computed value. Won't this throw off index lookups? (I might be >>>

Re: [GENERAL] How to hint 2 coulms IS NOT DISTINCT FROM each other

>> It might raise another problem, that the nulls are generated through LEFT >> JOINS where no rows are defined. Then the 0 or -1 value need to be >> a computed value. Won't this throw off index lookups? (I might be >> more confused in this area). > >Not following this. The nulls are generated

Re: [GENERAL] Recover from corrupted database due to failing disk

On 03/11/2016 14:20, Adrian Klaver wrote: The above does not make sense. You are having to recover because there was no backup and now you want to go forward without doing a backup? Hi Adrian, no, I don't want go forward without backups ;) Actually, the *first* thing I did after the vacuum

Re: [GENERAL] replication setup: advice needed

On Thu, Nov 3, 2016 at 8:17 PM, Dmitry Karasik wrote: > Dear all, > > I'd like to ask for help or advice with choosing the best replication > setup for > my task. > > I need to listen to continuous inserts/deletes/updates over a set of > tables, > and serve them over http,

Re: [GENERAL] High load average every 105 minutes

On 11/4/2016 1:45 AM, Nhan Nguyen wrote: The load average of the instance increase every 105 minutes even without any database. I’ve checked the scheduled jobs but couldn’t find anything suspicious. When the load average was at peak, I couldn’t see any process consuming resources. This

[GENERAL] High load average every 105 minutes

I have Postgresql 9.3 installed on AWS instance ubuntu 14.04 The load average of the instance increase every 105 minutes even without any database. I’ve checked the scheduled jobs but couldn’t find anything suspicious. When the load average was at peak, I couldn’t see any process consuming

Re: [GENERAL] Exclude pg_largeobject form pg_dump

Hi Amul, 2016-11-04 7:52 GMT+01:00 amul sul : > Hi Guillaume, > > I found following issues with this patch, sorry missed in previous post: > > You don't have to be sorry for me doing shitty things :) > #1 : > 43 @@ -392,6 +393,10 @@ main(int argc, char **argv) > 44

Re: [GENERAL] Exclude pg_largeobject form pg_dump

Hi Guillaume, I found following issues with this patch, sorry missed in previous post: #1 : 43 @@ -392,6 +393,10 @@ main(int argc, char **argv) 44 dopt.outputBlobs = true; 45 break; 46 47 + case 'B': /* Don't dump blobs */ 48 +