On 11/01/16 19:13, Oleg Bartunov wrote:
[...]
Some people don't understand all these issues with she/he, for
example, we in Russia are not really concern about this.
[...]
I started using 'Gender Appropriate' language long before this PC
nonsense started up. Back in those days the word 'he
On 11/01/16 15:00, Andrew Sullivan wrote:
Someone (never mind who, this isn't intended to be a blame-game
message) wrote:
Am I, as a mere male […] :-)
It was me.
The phrase "Mere Male" was title of a column I read in NZ Women's Weekly
that my mother bought when I was a teenager.
>>> An an
On Mon, Jan 11, 2016 at 03:27:43PM +0900, Michael Paquier wrote:
> On Mon, Jan 11, 2016 at 3:13 PM, Oleg Bartunov wrote:
> > Some people don't understand all these issues with she/he, for example, we
> > in Russia are not really concern about this.
>
> This depends on how the language is built.
On Mon, Jan 11, 2016 at 09:13:32AM +0300, Oleg Bartunov wrote:
> Some people don't understand all these issues with she/he, for example, we
> in Russia are not really concern about this.
Russian offers a "Mr.Bartunov" and a "Mrs.Bartunova". Am I mistaken ?
Karsten Hilbert
--
GPG key ID E4071346
On 1/11/16, Karsten Hilbert wrote:
> On Mon, Jan 11, 2016 at 09:13:32AM +0300, Oleg Bartunov wrote:
>
>> Some people don't understand all these issues with she/he, for example,
>> we
>> in Russia are not really concern about this.
>
> Russian offers a "Mr.Bartunov" and a "Mrs.Bartunova". Am I mist
On Mon, Jan 11, 2016 at 01:50:50AM -0800, Vitaly Burovoy wrote:
> > On Mon, Jan 11, 2016 at 09:13:32AM +0300, Oleg Bartunov wrote:
> >
> >> Some people don't understand all these issues with she/he, for example,
> >> we
> >> in Russia are not really concern about this.
> >
> > Russian offers a "Mr
On понедельник, 11 января 2016 г. 12:24:37 MSK, Karsten Hilbert wrote:
OTOH, there's a whole bunch of words denoting levels and
sublevels of politeness for each and every situation.
Politeness but not gender differences. Perhaps just for kids (-chan/-kun).
--
Yury Zhuravlev
Postgres Professional
On Mon, Jan 11, 2016 at 12:57:11PM +0300, Yury Zhuravlev wrote:
> >OTOH, there's a whole bunch of words denoting levels and
> >sublevels of politeness for each and every situation.
> Politeness but not gender differences. Perhaps just for kids (-chan/-kun).
Well, traditionally not. But kare/kano-
Hi,
We are evaluating BDR for a multi-master cross-datacenter replication, with 2
masters actually communicating across datacenter, supplemented by a local
in-datacenter replicas to provide HA.
Basically, something like
M <——> M
||
S S
I could run all nodes as
On Mon, Jan 11, 2016 at 3:36 AM, David G. Johnston
wrote:
> When executing a query using \watch in psql the first execution of the query
> includes "Title is [...]" when \pset title is in use. Subsequent executions
> do not. Once that first display goes off-screen the information in the
> title
pg_upgrade complains about not being able to find $libdir/plpython3
when upgrading a 9.4 cluster that has both python2 and python3 used.
Both the 9.4 and 9.5 PGs have been built from source with python2/3 in
the recommended way and the plpython3.so is present in /usr/local/pgsql/lib.
I dropped the
Small update: Today the missing "pgdg-keyring" has been added to the
"wily-pgdg" apt repository.
My problem is thereby mostly resolved! :-)
Now only waiting for a new "pgadmin3" package...
Thanks everyone (and especially the package maintainers)!
Best regards,
Henning.
--
Henning Hoefer
Soft
I'm evaluating the use of PostgreSQL to our production mission-critical
application that currently runs on SQL Server 2012.
There is a huge partitioned table of archived information that is
occasionally queried (+5TB) and are not required to be 24/7 online. An
eventual failure on the filesystem th
> On Jan 10, 2016, at 2:59 PM, Joshua D. Drake wrote:
>
> On 01/10/2016 10:44 AM, Regina Obe wrote:
>
>>> JD
>>
>> This may come as a big shock to many of you, but as a contributor
>> I don't care if you are racist, sexist, transphobic or whatever as long as
>> you
>
> I think this is reasona
Paul Jones writes:
> pg_upgrade complains about not being able to find $libdir/plpython3
> when upgrading a 9.4 cluster that has both python2 and python3 used.
No, that's not what the error message says:
> Could not load library "$libdir/plpython3"
> FATAL: Python major version mismatch in sess
Michael Paquier writes:
> On Mon, Jan 11, 2016 at 3:36 AM, David G. Johnston
> wrote:
>> When executing a query using \watch in psql the first execution of the query
>> includes "Title is [...]" when \pset title is in use. Subsequent executions
>> do not. Once that first display goes off-screen
On Mon, Jan 11, 2016 at 8:14 AM, Tom Lane wrote:
> Michael Paquier writes:
> > On Mon, Jan 11, 2016 at 3:36 AM, David G. Johnston
> > wrote:
> >> When executing a query using \watch in psql the first execution of the
> query
> >> includes "Title is [...]" when \pset title is in use. Subsequent
On Mon, Jan 11, 2016 at 4:14 AM, Michael Paquier
wrote:
> On Mon, Jan 11, 2016 at 3:36 AM, David G. Johnston
> wrote:
> > When executing a query using \watch in psql the first execution of the
> query
> > includes "Title is [...]" when \pset title is in use. Subsequent
> executions
> > do not.
"David G. Johnston" writes:
> On Mon, Jan 11, 2016 at 8:14 AM, Tom Lane wrote:
>> Perhaps we should replace the "Watch every Ns" text by the user-given
>> title if a title has been set? That would conserve screen space.
> âThe extra line doesn't both me and given the length of the timestamp I
On Mon, Jan 11, 2016 at 9:03 AM, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Mon, Jan 11, 2016 at 8:14 AM, Tom Lane wrote:
> >> Perhaps we should replace the "Watch every Ns" text by the user-given
> >> title if a title has been set? That would conserve screen space.
>
> > The extra
I am trying to install postgresql-9.5 on Ubuntu 15.10 but I am getting an
unmet dependency.
cat /etc/apt/sources.list.d/pgdg.list
deb http://apt.postgresql.org/pub/repos/apt/ wily-pgdg main
4.2.0-23-generic #28-Ubuntu SMP
~/r/a/src> sudo apt-get install postgresql-9.5
Reading package lists... Do
On 01/09/2016 01:15 PM, Scottix wrote:
I am trying to install postgresql-9.5 on Ubuntu 15.10 but I am getting
an unmet dependency.
Believe that is fixed now:
http://www.postgresql.org/message-id/CAG2W7jfm=rx1mG2-9uwPbBiBJ2Ag2kA1iRLp6=pkfvuqe7x...@mail.gmail.com
--
Adrian Klaver
adrian.kla..
Buford Tannen wrote:
Regina Obe wrote:
Josh informed me you guys are thinking about a CoC. Let me start off by
saying that I don't think you need one and in fact having one may be
dangerous. ...
So please whatever you do, ... do not
choose this one or anything that looks like it:
http://contr
Hi,
On Mon, Jan 11, 2016 at 10:10:23PM +1300, Gavin Flower wrote:
> The phrase "Mere Male" was title of a column I read in NZ Women's Weekly
> that my mother bought when I was a teenager.
That's nice. I still found it offensive enough in the context to
think it worthy of note. (I'm not really
>ISTM that if we develop a code of conduct, it would need to be designed to
> insulate the community and individuals within it from becoming targets of
> legal action. "Mike said I was bad at postgres, it hurt my consulting and I
> want to sue Joe for replying-all and upping the hit-count o
> We expect of everyone in our spaces to try their best to do the same in a
> kind and gentle manner. If you feel it's just a minor offense and the person
> didn't mean harm by it,
>
> simply ignore it unless the pattern of talk continues. If the person
> continues or they say something you feel is
Maybe Trump should write this
Brian,
>> We expect of everyone in our spaces to try their best to do the same
>> in a kind and gentle manner. If you feel it's just a minor offense and
>> the person didn't mean harm by it,
>>
>> simply ignore it unless the pattern of talk continues. If the person
>> continues or they say some
On 01/11/2016 10:16 AM, Bret Stern wrote:
Maybe Trump should write this
Unfortunately Trump would likely not follow the CoC.
Thank you for the troll.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
A
Hello,
A lot of good discussion has happened on this thread and as a whole I
think it has been determined that if done correctly, a CoC would not be
a bad idea. Of course we need to write one.
A CoC is about providing a safe, respectful, productive, and
collaborative place for any person who
Josh,
If we do write a CoC, can we give it a different acronym. I'm going to say
something very sensitive here, so don't think I am joking.
When I was 5 I was raped by a next door neighbor. Everytime I here people talk
about Cocs and how silencing they are I think about that.
Thanks,
Regina
On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote:
> HANDLING ISSUES
...
> If you have contributed nothing to our project and you make
> demands for change, we will try to tell you that kindly and
> request you to change or leave.
May I kindly ask for a bit more explanation on this one
On 01/11/2016 11:10 AM, Regina Obe wrote:
Josh,
If we do write a CoC, can we give it a different acronym. I'm going to say
something very sensitive here, so don't think I am joking.
When I was 5 I was raped by a next door neighbor. Everytime I here people talk
about Cocs and how silencing th
> Regina,
> Although I can appreciate your sensitivity to the terminology based on your
> experience (and I am very sorry to read about that), I don't think it is
> reasonable to change from an Industry Standard acronym on that basis.
> Sincerely,
> JD
Fair enough.
--
Sent via pgsql-g
There was a side thread in the CoC thread about expanding the dev community
and making it easier for new devs to get involved. I would think that a bug
tracker, especially one where bugs can be labeled as "Newbie Friendly"
could go a long way towards that goal.
Additionally, a proper bug tracker w
On 01/11/2016 11:18 AM, James Keener wrote:
There was a side thread in the CoC thread about expanding the dev
community and making it easier for new devs to get involved. I would
think that a bug tracker, especially one where bugs can be labeled as
"Newbie Friendly" could go a long way towards th
Anyone looking to get their feet wet in the backend code, please take a
look at
http://www.postgresql.org/message-id/568f03ef.4070...@bluetreble.com.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in
Gosh, I've got a lot of love for CoCs; I've heard great things, really
good things, some things, about CoCs, that some of them have been
really helping in a yuge way with some fantastic projects. Sometimes
some people, a lot of people, have said that I could write a CoC, and
you know, I think they'
> On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote:
>> HANDLING ISSUES
>...
>> If you have contributed nothing to our project and you make
>> demands for change, we will try to tell you that kindly and
>> request you to change or leave.
> May I kindly ask for a bit more explanation on
"Joshua D. Drake" writes:
> On 01/11/2016 11:18 AM, James Keener wrote:
>> Are there any technical reasons that the project doesn't use a bug
>> tracker (beyond pgsql-bugs)?
> on -hackers there is on an ongoing thread about this [1] but the long
> and short is a: It is a culture issue. Warning,
Sorry screwed up sending this email the first time. Trying again:
> On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote:
>> HANDLING ISSUES
>...
>> If you have contributed nothing to our project and you make
>> demands for change, we will try to tell you that kindly and
>> request you t
Geoff,
> Gosh, I've got a lot of love for CoCs; I've heard great things, really good
> things, some things, about CoCs, that some of them have been really helping
> in a yuge way with some fantastic projects.
> Sometimes some people, a lot of people, have said that I could write a CoC,
> and y
On 01/11/2016 12:07 PM, Tom Lane wrote:
"Joshua D. Drake" writes:
On 01/11/2016 11:18 AM, James Keener wrote:
Are there any technical reasons that the project doesn't use a bug
tracker (beyond pgsql-bugs)?
on -hackers there is on an ongoing thread about this [1] but the long
and short is a:
On 11 January 2016 at 20:13, Regina Obe wrote:
> While this is funny to some, I don't think it adds value to this
> conversation. I would consider it a derailment and not very helpful.
>
> If I had a Coc to point at, I would point at the section I feel you are
> violating.
If there were a CoC
"Regina Obe" writes:
> Sorry screwed up sending this email the first time. Trying again:
>> On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote:
>>> If you have contributed nothing to our project and you make
>>> demands for change, we will try to tell you that kindly and
>>> request you t
> Hmm. I'm not sure that telling us that should amount to an offense; such
a person might even have a good idea from time to time.
> Now, if the person is rude about it, that would be an offense, but that
should already be covered under other sections of the CoC no?
> Another possibly offensive
Geoff,
> If there were a CoC that would explicitly disallow occasional lighthearted
> humour to a non-development list that is intended to offend no-one then I
> would most definitely remove myself from such a project.
> Some may consider that a positive thing, but I would like to think that i
On 11 January 2016 at 21:11, Regina Obe wrote:
> The Coc allows light-hearted humor, I'm so disappointed you didn't get my
> clever punning in my last email. I thought it was a treasure.
Hah! The irony is I had deliberately avoided making the obvious gag
because I've been called out previously
On 1/11/2016 1:11 PM, Regina Obe wrote:
On further observation, I realize it can be used as a testcase to test the
strength of this Coc. So I stand corrected this is quite relevant and useful
to this discussion. In fact, I think we should package all these and use them
in regression tests fo
On 01/11/2016 01:20 PM, John R Pierce wrote:
On 1/11/2016 1:11 PM, Regina Obe wrote:
On further observation, I realize it can be used as a testcase to test
the strength of this Coc. So I stand corrected this is quite relevant
and useful to this discussion. In fact, I think we should package al
On Mon, Jan 11, 2016 at 2:58 PM, Regina Obe wrote:
> How would you feel about the original thread that started this.
>
> https://github.com/opal/opal/issues/941
I'm not interested in opal, and don't have time to read a thread
with (when I looked) 374 messages, but if the gist of it is that
they
Kevin Grittner wrote:
> On Mon, Jan 11, 2016 at 2:58 PM, Regina Obe wrote:
>
> > How would you feel about the original thread that started this.
> >
> > https://github.com/opal/opal/issues/941
>
> I'm not interested in opal, and don't have time to read a thread
> with (when I looked) 374 message
On 1/11/16, Saulo Merlo wrote:
> NEW QUERY:
>
> SELECT
> <>
> WHERE f.nfs_file_path IS NULL
> AND ((transaction_timestamp() AT TIME ZONE \'UTC\') > (f.st_mtime+ \'' .
> $fileMigrationMonthAge . ' months\' :: INTERVAL)) LIMIT 100;
>
> From: smerl...@outlook.com
> To: clavadetsc...@swisspug.org;
I don't know about others.
But this whole thread has completely gone off the original track. With so many
splinter topics. It has no hope of ever completing with any kind of resolution
satisfying even 10% of contributors.
Can be please stick to the core original topics? Whether we agree with
On 01/11/2016 01:36 PM, Alvaro Herrera wrote:
Kevin Grittner wrote:
On Mon, Jan 11, 2016 at 2:58 PM, Regina Obe wrote:
How would you feel about the original thread that started this.
https://github.com/opal/opal/issues/941
I'm not interested in opal, and don't have time to read a thread
wi
This might interest some members.
It has been announced by Intel's latest Skylake CPU has serious bug which hangs
applications with complex threading which postgresql could *potentially* fall
into. I don't know if anyone has experienced this or not.
"Hello All,
Intel has identified an issue
On Mon, Jan 11, 2016 at 3:42 PM, FarjadFarid(ChkNet)
wrote:
Five days (and I don't know how many posts) ago, there was this:
http://www.postgresql.org/message-id/20160106184818.gt21...@crankycanuck.ca
Which said in part:
> The other thing I note is that the IETF got
> most of these documents b
Hello,
Below please find a WIP CoC for the PostgreSQL.Org project:
PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC):
1. The CoC is to provide community guidelines for creating and enforcing
a safe, respectful, productive, and collaborative place for any person
who is willing t
"Regina Obe" writes:
> How would you feel about the original thread that started this.
> https://github.com/opal/opal/issues/941
> I would dismiss her as a troll and kindly say, don't tell us who we can have
> and who we can't.
Hm ... that thread makes me uncomfortable, because I can see both poi
Hello,
Below please find a WIP CoC for the PostgreSQL.Org project:
PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC):
1. The CoC is to provide community guidelines for creating and enforcing
a safe, respectful, productive, and collaborative place for any person
who is willing t
On 01/11/2016 02:00 PM, Joshua D. Drake wrote:
Hello,
Below please find a WIP CoC for the PostgreSQL.Org project:
PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC):
1. The CoC is to provide community guidelines for creating and enforcing
a safe, respectful, productive, and colla
Kevin Grittner writes:
> I'm going to give this a belated +1, and ignore any further posts on
> this thread.
> If someone wants to take the step of posting a concrete proposal,
> please start a new thread with a different subject line.
I thought we were already at that point; see Regina Obe's pos
On 01/11/2016 02:08 PM, Adrian Klaver wrote:
On 01/11/2016 02:00 PM, Joshua D. Drake wrote:
Hello,
Below please find a WIP CoC for the PostgreSQL.Org project:
PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC):
1. The CoC is to provide community guidelines for creating and enfor
Regina Obe wrote:
>
> If we do write a CoC, can we give it a different acronym.
> Notwithstanding the most regrettable childhood trauma, this request is
> exactly the kind of ridiculousness that the Political Correctness nonsense
> associated with CoCs that we should be worried about in the aft
Thanks Joshua for creating this list. Great starting point and hopefully points
to focus on to conclude this thread.
Here are my humble comments on them.
I think point two is already covered by respecting other people's opinion. At
times specially over email ,where we don't see others react
Kevin Grittner writes:
> On Mon, Jan 11, 2016 at 2:58 PM, Regina Obe wrote:
>> How would you feel about the original thread that started this.
>> https://github.com/opal/opal/issues/941
> I'm not interested in opal, and don't have time to read a thread
> with (when I looked) 374 messages, but if
On Mon, Jan 11, 2016 at 02:00:22PM -0800, Joshua D. Drake wrote:
> 3. A safe, respectful, productive and collaborative environment is free
> comments related to gender, sexual orientation, disability, physical
> appearance, body size or race.
... for of _off-topic_ comments related to ...
Since
> 3. A safe, respectful, productive and collaborative environment is free
> comments related to gender, sexual orientation, disability, physical
> appearance, body size or race.
I think you meant "free OF comments".
However it still picks a few special classes of complaint, some of
which cause am
> 3. A safe, respectful, productive and collaborative environment is free
of comments related to gender, sexual orientation, disability,
physical appearance,
body size or race.
why not
> 3. A safe, respectful, productive and collaborative environment is free
of ad hominem. (Tip: Ask your self "Wo
Adrian Klaver wrote:
> On 01/11/2016 02:00 PM, Joshua D. Drake wrote:
> >3. A safe, respectful, productive and collaborative environment is free
> >comments related to gender, sexual orientation, disability, physical
> >appearance, body size or race.
>
> Well that renders this thread:
>
> http:/
On 01/11/2016 02:22 PM, Brian Dunavant wrote:
3. A safe, respectful, productive and collaborative environment is free
comments related to gender, sexual orientation, disability, physical
appearance, body size or race.
I think you meant "free OF comments".
I did.
However it still picks a fe
ALL:
Please move comments to the new thread: WIP: CoC
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyo
(Sorry for the dup post. I felt having a clean thread without having to
cross-reference was worth the minor faux pas.)
> 3. A safe, respectful, productive and collaborative environment is free
of comments related to gender, sexual orientation, disability,
physical appearance,
body size or race.
w
On Mon, Jan 11, 2016 at 4:10 PM, Tom Lane wrote:
> Kevin Grittner writes:
>> If someone wants to take the step of posting a concrete proposal,
>> please start a new thread with a different subject line.
>
> I thought we were already at that point; see Regina Obe's posts.
Oh, are you referring t
Kevin Grittner writes:
> On Mon, Jan 11, 2016 at 4:10 PM, Tom Lane wrote:
>> I thought we were already at that point; see Regina Obe's posts.
> Oh, are you referring to this:?
> http://www.postgresql.org/message-id/001201d14c96$fc26ed70$f474c850$@pcorp.us
> For some reason that shows up as a quo
On 12/01/16 11:21, Karsten Hilbert wrote:
On Mon, Jan 11, 2016 at 02:00:22PM -0800, Joshua D. Drake wrote:
3. A safe, respectful, productive and collaborative environment is free
comments related to gender, sexual orientation, disability, physical
appearance, body size or race.
... for of _off
Dear all,
Please let's not be pedantic and expect absolute legalistic perfection in
the wordings that has been put forward.
No doubt we all understand the spirit and the purpose of the wording. Which
is when we are consulting in the community we
are not to here to discuss other people's gend
>> "3) A safe, respectful, productive and collaborative environment is
>> free of negative personal criticism directed at a member of a
>> community, rather than at the technical merit of a topic."
>>
> A safe, respectful, productive and collaborative environment is free
> of non-technical or per
On 01/11/2016 02:30 PM, James Keener wrote:
(Sorry for the dup post. I felt having a clean thread without having to
cross-reference was worth the minor faux pas.)
3. A safe, respectful, productive and collaborative environment is free
of comments related to gender, sexual orientation, disabili
On 01/11/2016 02:27 PM, Joshua D. Drake wrote:
On 01/11/2016 02:22 PM, Brian Dunavant wrote:
3. A safe, respectful, productive and collaborative environment is free
comments related to gender, sexual orientation, disability, physical
appearance, body size or race.
I think you meant "free OF co
On 01/11/2016 02:41 PM, Brian Dunavant wrote:
"3) A safe, respectful, productive and collaborative environment is
free of negative personal criticism directed at a member of a
community, rather than at the technical merit of a topic."
A safe, respectful, productive and collaborative environm
> So is life. We aren't here to wipe butts and change a diaper.
But the original isn't constructive of what to do. If I am attacked personally
I will feel offended, the point is what I do about it. Whining about bring
offended vs bringing it up and saying that it is not acceptable behaviour are
"Joshua D. Drake" writes:
> How about we meet in the middle:
> A safe, respectful, productive and collaborative environment is free
> of non-technical or personal comments related to gender, sexual
> orientation, disability, physical appearance, body size, race or
> personal attacks.
That's no
> 2. The CoC is not about being offended. The act of being offended is purely a
> recipient response and usually the offended individual is more interested in
> being a victim than moving forward.
Here is my latest version. Let me know if I should throw in a github repo so
it's easier to read
> A safe, respectful, productive and collaborative environment is one
that focuses on the technical merit of ideas and solutions rather than
on the person behind them.
I still prefer this wording as there is no need for us to list the ways in
which someone can personally be attacked. Should the l
On 1/11/16, Saulo Merlo wrote:
> Ok, thanks Vitaly.
> I need to create a TEXT or VARCHAR index.
> and another one with timestamptz
> How can I do?Thanks
How to create indexes of different types is written at [1].
But I thing you need something else. You have to create index on the
specified colum
On 01/11/2016 02:54 PM, Tom Lane wrote:
"Joshua D. Drake" writes:
How about we meet in the middle:
A safe, respectful, productive and collaborative environment is free
of non-technical or personal comments related to gender, sexual
orientation, disability, physical appearance, body size, rac
> We value the opinions of members who have contributed most more than we value
> the opinions of others.
A CoC is not the place to say some animals are more equal than others. A core
commiter calling someone the n- or b- words is just as bad as me, a non
commiter (if not worse!)
> While we do
Why must it be free of personal comments?
"Tom, I like the way you handed this issue. Good work!" Is a personal comment.
Why do we need lists? What specifically is wrong with "that focuses on the tech
and not the person" version?
Jim
On January 11, 2016 6:04:03 PM EST, "Joshua D. Drake"
wrot
> """ A safe, respectful, productive and collaborative environment is free of
> non-technical or personal comments related to gender, sexual orientation,
> disability, physical appearance, body size or race. """
I really think you should leave out the whole " gender, sexual orientation,
disabi
On Mon, Jan 11, 2016 at 10:04:16AM -0500, Tom Lane wrote:
/tmp/mutt-mayon-1000-19386-284b6a00794950f414
> Paul Jones writes:
> > pg_upgrade complains about not being able to find $libdir/plpython3
> > when upgrading a 9.4 cluster that has both python2 and python3 used.
>
> No, that's not what th
tl;dr;
* Modified #2 to be less harsh.
* Modified #3 with TGL and James comments
* Did not remove examples as I believe they are vital to the success
I saw Regina's post, I believe it is good for context but I also believe
that something concise and to the point is the better path.
PostgreSQL
Thanks Vitaly for all your help. I'll have a very deep look on the links you
have provided. In the meantime, I'll also post here what I need.. IF you could
help one more time, would be very very nice.
Thank you again.
This can either be nfs_file_path or nfs_migration_date (both new columns).
Ad
Paul Jones writes:
> On Mon, Jan 11, 2016 at 10:04:16AM -0500, Tom Lane wrote:
>> It looks like pg_upgrade tries to load all libraries from functions in
>> any database in the old cluster into a single session in the new cluster,
>> which will fail in a scenario like this even if you keep python2
> We value the opinions of members who have contributed most more than we value
> the opinions of others.
> A CoC is not the place to say some animals are more equal than others. A core
> commiter calling someone the n- or b- words is just as bad as me, a non
> commiter (if not worse!)
Yes
Regina Obe wrote:
If I had a Coc to point at, I would point at the section I feel you are
violating.
+1 funny!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Regina Obe wrote:
If we do write a CoC, can we give it a different acronym.
Notwithstanding the most regrettable childhood trauma, this request is
exactly the kind of ridiculousness that the Political Correctness
nonsense associated with CoCs that we should be worried about in the
aftermath
Geoff Winkless wrote:
On 11 January 2016 at 20:13, Regina Obe wrote:
While this is funny to some, I don't think it adds value to this conversation.
I would consider it a derailment and not very helpful.
If I had a Coc to point at, I would point at the section I feel you are
violating.
If
> On 12 Jan 2016, at 0:16, Joshua D. Drake wrote:
>
> 3. A safe, respectful, productive and collaborative environment is free of
> non-technical or personal comments, for example ones related to gender,
> sexual orientation, disability, physical appearance, body size, race or
> personal attac
On Mon, 11 Jan 2016 11:00:23 -0800
"Joshua D. Drake" wrote:
> A CoC is not about being offended. The act of being offended is
> purely a recipients response and usually because the recipient is
> more interested in being a victim than moving forward.
I've seen text like the preceding in over 10
1 - 100 of 122 matches
Mail list logo
