Re: [GENERAL] Install pgAudit extension

2016-12-12 Thread Dylan Luong
Hi Thanks for your reply. I have managed to get pgAudit install and I believe is working as I can see audit logs in my log files. I like to now install the PostgreSQL Audit Log Analyzer. Is there a similar rpm for the PostgreSQL Audit Log Analyser? Regards Dylan -Original Message-

Re: [GENERAL] ora2pg - Java Message Service (JMS) Type

2016-12-12 Thread Julien Rouhaud
On Mon, Dec 12, 2016 at 04:15:59PM +, Joanna Xu wrote: > On Fri, Dec 11, 2016 12:43 PM, Julien Rouhaud wrote: > >>I forwarded your mail to the author, since he's not on this mailing-list. > >>This issue should be fixed with commit >

Re: [GENERAL] ora2pg - Java Message Service (JMS) Type

2016-12-12 Thread Joanna Xu
On Fri, Dec 11, 2016 12:43 PM, Julien Rouhaud wrote: >>I forwarded your mail to the author, since he's not on this mailing-list. >>This issue should be fixed with commit https://github.com/darold/ora2pg/commit/2c22d377e9f90fa6fa83cfe1fbead9eb3396a0f3. >>If this bugfix is not enough or

Re: [GENERAL] btree gist indices, null and open-ended tsranges

2016-12-12 Thread Adrian Klaver
On 12/11/2016 11:34 PM, Chris Withers wrote: > On 01/12/2016 12:12, Francisco Olarte wrote: >> On Thu, Dec 1, 2016 at 12:56 PM, Chris Withers >> wrote: >>> So, first observation: if I make room nullable, the exclude >>> constraint does >>> not apply for rows that have a

Re: [GENERAL] schema advice for event stream with tagging and filtering

2016-12-12 Thread Chris Withers
On 16/08/2016 15:10, Ilya Kazakevich wrote: An event is a row with a primary key along the lines of (colo, host, category) and an associated set of tags, where each tag has a type and a value (eg: {"color": "red", "owner": "fred", "status": "open"...}). What about simple table with several

Re: [GENERAL] WAL

2016-12-12 Thread Torsten Förtsch
On Mon, Dec 12, 2016 at 12:37 PM, Albe Laurenz wrote: > Torsten Förtsch wrote: > > if I do something like this: > > > > BEGIN; > > UPDATE tbl SET data='something' WHERE pkey='selector'; > > UPDATE tbl SET data=NULL WHERE pkey='selector'; > > COMMIT; > > > > Given

Re: [GENERAL] WAL

2016-12-12 Thread Albe Laurenz
Torsten Förtsch wrote: > if I do something like this: > > BEGIN; > UPDATE tbl SET data='something' WHERE pkey='selector'; > UPDATE tbl SET data=NULL WHERE pkey='selector'; > COMMIT; > > Given 'selector' actually exists, I get a separate WAL entry for each of the > updates. My question is, >

Re: [GENERAL] btree gist indices, null and open-ended tsranges

2016-12-12 Thread Chris Withers
On 01/12/2016 12:12, Francisco Olarte wrote: On Thu, Dec 1, 2016 at 12:56 PM, Chris Withers wrote: So, first observation: if I make room nullable, the exclude constraint does not apply for rows that have a room of null. I guess that's to be expected, right? I would

Re: [GENERAL] huge table occupation after updates

2016-12-12 Thread t.dalpo...@gmail.com
Il 12/12/2016 02:42, David G. Johnston ha scritto: On Saturday, December 10, 2016, Tom DalPozzo > wrote: ​I have one direct DB client (let's name it MIDAPP) only. This client of the DB is a server for up to 1 final

[GENERAL] WAL

2016-12-12 Thread Torsten Förtsch
Hi, if I do something like this: BEGIN; UPDATE tbl SET data='something' WHERE pkey='selector'; UPDATE tbl SET data=NULL WHERE pkey='selector'; COMMIT; Given 'selector' actually exists, I get a separate WAL entry for each of the updates. My question is, does the first update actually hit the