Hi Melvin
From: Melvin Davidson [mailto:melvin6...@gmail.com]
Sent: Donnerstag, 31. Mai 2018 15:53
To: Charles Clavadetscher
Cc: pgsql-generallists.postgresql.org
Subject: Re: Question on disk contention
On Thu, May 31, 2018 at 1:13 AM, Charles Clavadetscher
mailto:clavadetsc...@s
Thank you Adrian,
in answer to response in link:
This connection string is not working for me.
Ma macro is:
Public Sub InitConnect()
>
>
>> On Error GoTo ErrHandler
>
>
>> Dim dbCurrent As DAO.Database
>
> Dim qdf As DAO.QueryDef
>
> Dim rst As DAO.Recordset
>
> Dim cnn As Objec
On Sunday, June 3, 2018, George Neuner wrote:
> On Sun, 03 Jun 2018 17:47:58 -0400, Tom Lane
> wrote:
>
> >Benjamin Scherrey writes:
> >
> >> Another more specific factual question - have there been incidents
> within
> >> the active Postgresql community where behaviour by individuals who are
>
On Sun, 03 Jun 2018 17:47:58 -0400, Tom Lane
wrote:
>Benjamin Scherrey writes:
>
>> Another more specific factual question - have there been incidents within
>> the active Postgresql community where behaviour by individuals who are
>> participants in the community have conducted themselves in a
> On Jun 3, 2018, at 7:08 PM, Gavin Flower
> wrote:
>
> On 04/06/18 07:32, Adrian Klaver wrote:
>> On 06/03/2018 11:29 AM, Tom Lane wrote:
>>> Two years ago, there was considerable discussion about creating a
>>> Code of Conduct for the Postgres community, as a result of which
>>> the core tea
Some people are not paying attention and are sending code-of-conduct comments to
all lists, not just pgsql-general, but -hackers and -advocacy too.
I've seen 3 of these so far today.
This is a reminder to please send the comments to pgsql-general only.
-- Darren Duncan
On 2018-06-03 11:29 AM,
On Jun 3, 2018, at 16:08 , Gavin Flower wrote:
>
> Be very careful in attempting to codify 'correct' behaviour!
+1 this is a distraction.
On 04/06/18 07:32, Adrian Klaver wrote:
On 06/03/2018 11:29 AM, Tom Lane wrote:
Two years ago, there was considerable discussion about creating a
Code of Conduct for the Postgres community, as a result of which
the core team announced a plan to create an exploration committee
to draft a CoC [1].
On 06/03/2018 04:54 PM, Berend Tober wrote:
Tom Lane wrote:
Two years ago, there was considerable discussion about creating a
Code of Conduct for the Postgres community...
We are now asking for a final round of community comments...
I really like that this was included: "Any allegations that
On 06/03/2018 02:47 PM, Tom Lane wrote:
Benjamin Scherrey writes:
Is there some archive of the discussion that brought on this effort and the
considerations of the committee itself? I wish I had seen the earlier
announcements in 2016 as I would have definitely participated.
If you poke around
Jeff Janes writes:
> On Thu, May 31, 2018 at 8:23 AM, C GG wrote:
>
> In the meantime, I did what I promised Adrian Klaver I would do and I added
>> the AD servers to the /etc/hosts file. That had an immediate and dramatic
>> effect on the performance. That confirms (at least to me) that DNS
>
Tom Lane wrote:
Two years ago, there was considerable discussion about creating a
Code of Conduct for the Postgres community...
We are now asking for a final round of community comments...
I really like that this was included: "Any allegations that prove not to be substantiated...will be
view
Benjamin Scherrey writes:
> Is there some archive of the discussion that brought on this effort and the
> considerations of the committee itself? I wish I had seen the earlier
> announcements in 2016 as I would have definitely participated.
If you poke around in our mailing list archives for earl
On 06/03/2018 11:29 AM, Tom Lane wrote:
Two years ago, there was considerable discussion about creating a
Code of Conduct for the Postgres community, as a result of which
the core team announced a plan to create an exploration committee
to draft a CoC [1]. That process has taken far longer than
Is there some archive of the discussion that brought on this effort and the
considerations of the committee itself? I wish I had seen the earlier
announcements in 2016 as I would have definitely participated.
Another more specific factual question - have there been incidents within
the active Post
On 06/01/2018 03:14 PM, Justin Pryzby wrote:
Before I forget any more, this is a brain of issues/considerations/concerns
with our (partial) transition to partitioned tables over the last ~9 months. I
believe these are all documented behaviors, but could be seen by users as a
gratuitious/unexpect
Two years ago, there was considerable discussion about creating a
Code of Conduct for the Postgres community, as a result of which
the core team announced a plan to create an exploration committee
to draft a CoC [1]. That process has taken far longer than expected,
but the committee has not been i
On Thu, May 31, 2018 at 9:19 AM, Ashu Pachauri wrote:
> There was too much noise in the pg_stat_activity output, so I did not post
> it. I'll collect the output again and post.
>
> But, when I checked in pg_stat_activity, PID 18317 is the session that's
> running the ALTER statement and it was sh
On Thu, May 31, 2018 at 8:23 AM, C GG wrote:
In the meantime, I did what I promised Adrian Klaver I would do and I added
> the AD servers to the /etc/hosts file. That had an immediate and dramatic
> effect on the performance. That confirms (at least to me) that DNS
> resolution was playing a larg
19 matches
Mail list logo
