Re: [COMMITTERS] pgsql: Row-Level Security Policies (RLS)

2014-09-20 Thread Dimitri Fontaine
the feature? I'm not seeing any high level description of it with use case examples… and I think this feature does warrant a high level introductory chapter in the manual… Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent v

Re: [COMMITTERS] pgsql: pg_test_fsync: update output to show usecs/op clearer

2013-05-02 Thread Dimitri Fontaine
Bruce Momjian writes: > My point is that tools would need to adjust to output not knowing if > they are getting UTF8 output, e.g.: Ah, yes. Or use "LANG=C pg_test_fsync" or the documented stanza that always works in scripts as it forces the output to something predictable? --

Re: [COMMITTERS] pgsql: pg_test_fsync: update output to show usecs/op clearer

2013-05-02 Thread Dimitri Fontaine
echo 'µsec' | awk '/µsec/' µsec Maybe there's no practical problem here, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subsc

Re: [COMMITTERS] pgsql: pg_test_fsync: update output to show usecs/op clearer

2013-05-02 Thread Dimitri Fontaine
and ouput µsec, as it's meant to be? Then google is useful again, for the smaller number of people who would need it. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-30 Thread Dimitri Fontaine
nough to cover and not covered already. >> Finally, I've been surprised to find out that those cases are only >> triggering for "ddl_event_start" (and not "ddl_event_end"), I think >> that's a bug we should be fixing: > > Agreed, I fixed it.

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-12 Thread Dimitri Fontaine
e master's branch. The two other cases should just be moved to the later switch so that both start and end triggers happen. Or maybe I'm missing something here. Given that it might as well be the case, I did only refactor the code keeping its current behavior rather than fixing what I t

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-09 Thread Dimitri Fontaine
ust writing it down. Thanks. >> Do you want me to work on a patch at the end of this week? > > As (one of) the committer(s) responsible for this code, I do, thanks. Will do. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent vi

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-09 Thread Dimitri Fontaine
ity switch. Do you want me to work on a patch at the end of this week? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-09 Thread Dimitri Fontaine
f one invocation of the trigger stuff before and > after the switch. That needs either lots of code duplication or some smarts that I don't see yet, because of the EventTriggerSupportsObjectType stuff. Anyways I'm not much into C macrology myself… At best I can find some time and work o

Re: [HACKERS] [COMMITTERS] pgsql: Add sql_drop event for event triggers

2013-04-09 Thread Dimitri Fontaine
t code, and we can even continue using the current macro. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers

Re: [COMMITTERS] pgsql: Get rid of USE_WIDE_UPPER_LOWER dependency in trigram constructi

2013-04-08 Thread Dimitri Fontaine
nary life's easier. That would also be an excuse for the project to install some upgrade material on the old server, which has been discussed in the past for preparing pg_upgrade when we have a page format change. What do you think? -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Ex