On 15/09/18 08:17, Tom Lane wrote:
Yeah, this. The PG community is mostly nice people, AFAICT. I'll be
astonished (and worried) if the CoC committee finds much to do. We're
implementing this mostly to make newcomers to the project feel that
it's a safe space.
Agreed. However I think the
On 9/14/18 11:13 AM, Robert Haas wrote:
On Fri, Sep 14, 2018 at 11:10 AM, Dave Page wrote:
That wording has been in the published draft for 18 months, and noone
objected to it that I'm aware of. There will always be people who don't like
some of the wording, much as there are often people who
On 9/14/18 11:21 AM, Peter Geoghegan wrote:
On Fri, Sep 14, 2018 at 11:06 AM, Dimitri Maziuk wrote:
Personally I would like that. Others might prefer an invitation to
unsubscribe or forever hold their peace, I could live with that too, but
I believe explicit opt-ins are preferable to opt-outs.
Tom & Jerry,
Thanks a lot for information!
On Monday (weekends don't have the same load patterns compared to business
days) I will take a look at ` pg_prepared_xacts` that seems to expose Jerry's
suggestion on xacts. Replication slots don't apply to 9.2.X from what I could
investigate so I
Martin Mueller writes:
> Which makes me say again "Where is the problem that needs solving?"
We've re-litigated that point in each burst of CoC discussion for the
last two-plus years, I think. But, one more time:
* So far as the mailing lists alone are concerned, we likely don't really
need a
That is quite true: the very high quotient of helpful prose and very low
quotient of inappropriate language is striking--much like the TEI list of which
I long have been a member, and unlike the MySQL list, which has a non-trivial
(though not serious) boorish component.
Which makes me say
On Sat, Sep 15, 2018 at 12:11:37PM -0400, Melvin Davidson wrote:
> How about we just simplify the code of conduct to the following:
> Any member in the various PostgreSQL lists is expected to maintain
> respect to others and not use foul language. A variation from
> the previous sentence shall be
On Sat, Sep 15, 2018 at 04:24:38PM +, Martin Mueller wrote:
> What counts as foul language has changed a great deal in the last two
> decades.
> You could always tie it to what is printable in the New York Times, but that
> too is changing. I could live with something like “Be considerate,
What counts as foul language has changed a great deal in the last two decades.
You could always tie it to what is printable in the New York Times, but that
too is changing. I could live with something like “Be considerate, and if you
can’t be nice, be at least civil”.
From: Melvin Davidson
How about we just simplify the code of conduct to the following:
Any member in the various PostgreSQL lists is expected to maintain
respect to others and not use foul language. A variation from
the previous sentence shall be considered a violation of the CoC.
On Sat, Sep 15, 2018 at 11:51 AM Tom
Bruce Momjian writes:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but nothing is perfect.
Yeah, a busybody CoC
On Sat, Sep 15, 2018 at 11:32:06AM -0400, Bruce Momjian wrote:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but
On Sat, Sep 15, 2018 at 08:44:10AM +0200, Chris Travers wrote:
> The protection there is a culturally diverse code of conduct committee who can
> then understand the relationship between politics and culture. And just to
> note, you can't solve problems of abuse by adopting mechanistically
Hi
Thank you for the answer, after a longer tracing, (go based and printing pg
queries to log, I realize that it happens on a different place that I
thought it does.
Ido
On Sat, Sep 15, 2018 at 12:13 AM Adrian Klaver
wrote:
> On 9/14/18 12:11 PM, ik wrote:
> > Hello,
> >
> > Not sure that
Dear all,
On Fri, Sep 14, 2018 at 5:18 PM Tom Lane wrote:
> Robert Haas writes:
> > It's not clear to me that there IS a general consensus here. It looks
> > to me like the unelected core team got together and decided to impose
> > a vaguely-worded code of conduct on a vaguely-defined group
Hello,
I'm trying to generate a table with information from a temporary view
that simply selects a subset of columns from a persistent view in a
given schema. The persistent view joins a number of tables with columns
that may or may not have a description entered.
Here's my attempt at listing
Hi
so 15. 9. 2018 v 9:39 odesílatel Arup Rakshit napsal:
> Here is a explain plan of a very simple query:
>
> aruprakshit=# explain analyze select first_name, last_name from users
> where lower(state) = 'colorado';
> QUERY PLAN
>
>
Here is a explain plan of a very simple query:
aruprakshit=# explain analyze select first_name, last_name from users where
lower(state) = 'colorado';
QUERY PLAN
On Sat, Sep 15, 2018 at 4:47 AM James Keener wrote:
>
>
> The preceding's pretty simple. An attacker goes after an individual,
>> presumably without provocation and/or asymetrically. The attacked
>> person is on this mailing list. IMHO this attacker must choose between
>> continuing his attacks,
19 matches
Mail list logo
