On Sun, Jul 9, 2017 at 2:35 AM, Mark Rofail wrote:
> * What I am working on*
>
>- since we want to create an index on the referencing column, I am
>working on firing a 'CREATE INDEX' query programatically right after
>the 'CREATE TABLE' query
>- The problem I ran into is how to sp
On Sun, Jul 09, 2017 at 11:46:03AM +1200, Thomas Munro wrote:
> On Sat, Jul 8, 2017 at 8:42 PM, David Fetter wrote:
> > Using the script attached, I'm getting this very odd result set below.
> >
> > Audit records from COPY to the "foo bar" table aren't getting
> > recorded, but audit records from
On Sat, Jul 8, 2017 at 8:42 PM, David Fetter wrote:
> Using the script attached, I'm getting this very odd result set below.
>
> Audit records from COPY to the "foo bar" table aren't getting
> recorded, but audit records from COPY to the baz table are.
Thanks for the bug report. I think it's the
* What I am working on*
- since we want to create an index on the referencing column, I am
working on firing a 'CREATE INDEX' query programatically right after the
'CREATE TABLE' query
- The problem I ran into is how to specify my Strategy (
GinContainsElemStrategy) within the CR
On Wednesday, June 14, 2017, Michael Paquier
wrote:
> On Tue, Jun 13, 2017 at 4:50 PM, Craig Ringer > wrote:
> > On 13 June 2017 at 14:33, Michael Paquier > wrote:
> >> Those come from stop_streaming in pg_receivewal.c. Shouldn't those
> >> messages only show up to the user if --verbose is used
The PDF-version of the documentation has content-'frame' displayed on
the left-hand side (I'm viewing with okular; I assmume it will be
similar in most viewers).
That content displays a treeview down to the main entries/lemmata, like
'CREATE TABLE'. It doesn't go any deeper anymore.
There u
On Sat, Jul 8, 2017 at 9:06 AM, Amit Kapila wrote:
> On Sat, Jul 8, 2017 at 8:52 AM, Robert Haas wrote:
>> On Thu, Jul 6, 2017 at 5:54 AM, Kyotaro HORIGUCHI
>> wrote:
>>> Check for INIT_FORKNUM appears both accompanied and not
>>> accompanied by check for RELPER.._UNLOGGED, so I'm not sure which
Hi Alvaro,
> Hi Tatsuo.
>
> There's definitely an important concern here that should be addressed:
> how poolers/proxies/middleware/etc can deal with SCRAM, specifically
> in the context of channel binding.
>
> If there is to be a single connection from client to PostgreSQL
>
Folks,
Using the script attached, I'm getting this very odd result set below.
Audit records from COPY to the "foo bar" table aren't getting
recorded, but audit records from COPY to the baz table are.
Best,
David.
\i copy_oddity.sql
CREATE TABLE
COMMENT
CREATE FUNCTION
CREATE FUNCTION
CREATE EV