Hello Dmitry
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Dmitry Vasilyev
> Sent: Freitag, 9. Oktober 2015 11:52
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Postgres service stops when I kill client
Hello
> Npgsql supports sending multiple SQL statements in a single packet via the
> extended protocol. This works fine, but when the second query SELECTs a value
> modified by the first's UPDATE, I'm getting a result as if the
> UPDATE hasn't yet occurred.
Looks like the first updating
<pete...@gmx.net>; pgsql-hackers
> <pgsql-hackers@postgresql.org>; Charles Clavadetscher
> <clavadetsc...@swisspug.org>
> Subject: Re: [HACKERS] unclear about row-level security USING vs. CHECK
>
> On Mon, Sep 28, 2015 at 3:15 PM, Stephen Frost <sfr...@snowman.net&
com>
> Cc: pgsql-hackers <pgsql-hackers@postgresql.org>; Charles Clavadetscher
> <clavadetsc...@swisspug.org>
> Subject: Re: [HACKERS] unclear about row-level security USING vs. CHECK
>
> * Peter Eisentraut (pete...@gmx.net) wrote:
> > I see. But it is a
Hello Peter
> I'm testing the new row-level security feature. I'm not clear on the
> difference between the USING and CHECK clauses in the CREATE POLICY
> statement.
>
> The documentation says:
>
> """
> A policy grants the ability to SELECT, INSERT, UPDATE, or DELETE rows
> which match the
Hello Jim
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-
> ow...@postgresql.org] On Behalf Of Charles Clavadetscher
> Sent: Dienstag, 15. September 2015 07:35
> To: Jim Nasby <jim.na...@bluetreble.com>; pgsql-hackers@postgre
Hi Stephen
> On 15.09.2015, at 17:13, Stephen Frost <sfr...@snowman.net> wrote:
>
> Charles,
>
> * Charles Clavadetscher (clavadetsc...@swisspug.org) wrote:
>> Yes, that helped a lot! In the attachment now a single patch file
>> with all changes.
>
>
Hello
In PostgreSQL it is possible to attach comments to almost everything. This
made it possible for us to integrate the wiki that we use for our technical
documentation directly with the database using the MediaWiki [1] extensions
ExternalData [2] and MagicNoCache [3]. The result is a
Hello Àlvaro
On 14/09/2015 20:02, Alvaro Herrera wrote:
Jim Nasby wrote:
On 9/14/15 8:59 AM, Charles Clavadetscher wrote:
To long time PostgreSQL developers this may look straightforward. For the
moment I am not even sure if that is correct and if there are other places
that would need
Hello Jim
On 14/09/2015 19:23, Jim Nasby wrote:
On 9/14/15 8:59 AM, Charles Clavadetscher wrote:
Hello
In PostgreSQL it is possible to attach comments to almost everything.
This
made it possible for us to integrate the wiki that we use for our
technical
documentation directly
this helps.
Regards
Charles
-Original Message-
From: pgsql-docs-ow...@postgresql.org
[mailto:pgsql-docs-ow...@postgresql.org] On Behalf Of Charles Clavadetscher
Sent: Sonntag, 13. September 2015 07:36
To: pgsql-d...@postgresql.org
Subject: [DOCS] Missing COMMENT ON POLICY
Hello
Lately I am
Stephen
On 13/09/2015 15:26, Charles Clavadetscher wrote:
Hello Stephen
On 13/09/2015 14:49, Stephen Frost wrote:
Charles,
Just FYI, on these lists, we'd prefer it if you wouldn't top-post.
* Charles Clavadetscher (clavadetsc...@swisspug.org) wrote:
Yes, of course. I will take care
hen Frost
> Sent: Sonntag, 13. September 2015 14:31
> To: Charles Clavadetscher <clavadetsc...@swisspug.org>
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [DOCS] Missing COMMENT ON POLICY
>
> Charles,
>
> * Charles Clavadetscher (clavadetsc...@swisspug.org
Hello Stephen
On 13/09/2015 14:49, Stephen Frost wrote:
Charles,
Just FYI, on these lists, we'd prefer it if you wouldn't top-post.
* Charles Clavadetscher (clavadetsc...@swisspug.org) wrote:
Yes, of course. I will take care of that and send a new patch.
Thanks!
Who will then git push
Hi Stephen
On 13/09/2015 16:56, Stephen Frost wrote:
Charles,
* Charles Clavadetscher (clavadetsc...@swisspug.org) wrote:
I noticed that the position of the parameter "policy_name" in the
description list of parameters was not at the (alphabetically)
correct position.
15 matches
Mail list logo