Re: [GENERAL] Hiding users and databases

2014-10-17 Thread Bruce Momjian
On Fri, Oct 17, 2014 at 01:48:25PM +1100, Ross Dougherty wrote: > Hi all, > > We run database servers that each contain multiple customer databases. > We would like to give customers access to their own database but even > though they are unable to connect to the databases of other customers > due

[GENERAL] Integrating C++ singletons into postgresql extensions???

2014-10-17 Thread Stephen Woodbridge
Hi, I've been writing C++ code that needs to get wrapped into a postgresql extension and it has a few singleton classes like: 1. Config object that holds some general configuration information. 2. Stats object for global stats collection. 3. Logger object for enabling/disabling debug logging t

Re: [GENERAL] Will pg_repack improve this query performance?

2014-10-17 Thread aron123
Thanks for share… - harry -- View this message in context: http://postgresql.1045698.n5.nabble.com/Will-pg-repack-improve-this-query-performance-tp5823051p5823385.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-ge

[GENERAL] Hiding users and databases

2014-10-17 Thread Ross Dougherty
Hi all, We run database servers that each contain multiple customer databases. We would like to give customers access to their own database but even though they are unable to connect to the databases of other customers due to connect grants they are still able to see all other databases and users

Re: [GENERAL] PgAgent binary distribution for Centos 6.5

2014-10-17 Thread Devrim Gündüz
Hi, On Mon, 2014-08-11 at 19:33 +0800, Jen Sing Choe wrote: > does anyone have link to download pgagent binary distribution for centos ? > i tried on building the tar source but stuck on resolving the wxGTK > (wxWidget) dependencies. I pushed pgagent 3.4.0 RPMs to PostgreSQL RPM repo today: http

Re: [GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread Albe Laurenz
Jerome Wagner wrote: [wants to access an application server farm with FDW] > Clearly, I am trying to see how I could twist the fdw wrappers into a sort of > manhole inside the > application, without resorting to a classic event based mechanism. That's too metaphorical for me to understand. > I c

Re: [GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread Jerome Wagner
Hello Albe, Thanks for your answer. The application is an application that is a sort of supervisor of sub applications, mainly web oriented. It manage access rights, update versions of web services, launch services, .. No the data is not sharded across the servers, but each server can have its o

Re: [GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread Jerome Wagner
Hello John, Thanks for your answer. I am also considering a publish/subscribe MQ based solution (and this may be indeed needed for queuing RPCs). the data I would like to access R/W is more like - configuration data - states of different state machines - cache values for some keys (reading, inv

Re: [GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread Albe Laurenz
Jerome Wagner wrote: > I am considering (postgres 9.3+) the idea of opening a R/W access into a > clustered application by > creating one fdw server from a central database to each server a cluster. > > That would imply opening a port on each server inside the application, > listening for incomi

Re: [GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread John R Pierce
On 10/17/2014 2:35 AM, Jerome Wagner wrote: Hello, I am considering (postgres 9.3+) the idea of opening a R/W access into a clustered application by creating one fdw server from a central database to each server a cluster. That would imply opening a port on each server inside the application

[GENERAL] FDW wrapper for clustered app management

2014-10-17 Thread Jerome Wagner
Hello, I am considering (postgres 9.3+) the idea of opening a R/W access into a clustered application by creating one fdw server from a central database to each server a cluster. That would imply opening a port on each server inside the application, listening for incoming connections from the dat