Re: [GENERAL] Code of Conduct: Is it time?

Tom Lane wrote: > In my admittedly-limited experience with dealing with such problems, > it's a lot easier to achieve positive results if you can discuss > issues in private, before people's positions harden. > > In short, I wouldn't characterize that complainant as "a troll" for > the substance o

Re: [GENERAL] WIP: CoC

Jim, > That has nothing to do with the Code of Conduct, though. The community > accepting Tom saying "no" to Feature X is vastly different than the community > not calling Tom out for being mean. > The CoC is about the later situation and not the prior; and the community > should call Tom out

[GENERAL] Giving error for function

Hi, I am getting the below error while I am running the below function "add_po_doc_hist", for "c_company" cursor, please suggest what is wrong with code. ERROR: relation "c_company" does not exist CONTEXT: compilation of PL/pgSQL function "add_po_doc_hist" near line 11 ** Error

Re: [GENERAL] WIP: CoC

[ just a few comments on specific points ] "Greg Sabino Mullane" writes: >> 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. > Too defensive; not

Re: [GENERAL] Request - repeat value of \pset title during \watch interations

On Tue, Jan 12, 2016 at 1:15 AM, David G. Johnston wrote: > 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

Re: [GENERAL] WIP: CoC V3

Any reason not to just adopt the contributor covenant? http://contributor-covenant.org/ tl;dr; * Removed #6 (Social Justice) 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,

Re: [GENERAL] WIP: CoC V3

tl;dr; * Removed #6 (Social Justice) 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 to contribute in a safe, respec

Re: [GENERAL] Building PostgreSQL in Eclipse on Windows

On 1/11/2016 6:21 PM, John R Pierce wrote: wait, are you trying to USE postgres on Eclipse on Windows, or BUILD it ?I would use the enterprisedb build of postgres-for-windows, and then you just need to install the appropriate postgresql jdbc jar file into Eclipse to be able to use it from y

[GENERAL] row-level security, views and materialized views?

Hi, has there been any discussion as to supporting row-level security policies on materialized views? I didn't have much luck searching on this topic. I see that PostgreSQL 9.5 refuses to create a policy on a materialized view, consistent with the documentation focusing only on tables. First off,

Re: [GENERAL] Building PostgreSQL in Eclipse on Windows

On 1/11/2016 5:32 PM, Igal @ Lucee.org wrote: Can anyone help me figure out how to run/debug PostgreSQL in Eclipse on Windows? This is a cross post with http://stackoverflow.com/questions/34733991/building-postgresql-in-eclipse-on-windows : I'm trying to build|PosgreSQL|in Eclipse CDT

Re: [GENERAL] WIP: CoC

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 (Wow. I cannot recall a time I've seen so many posts that just make me shake my head in sadness. It's painfully obvious that a code of conduct is way outside the wheelhouse of many of the participants in this thread.) > Below please find a W

Re: [GENERAL] WIP: CoC

>> That has nothing to do with the Code of Conduct, though. The >> community accepting Tom saying "no" to Feature X is vastly >> different than the community not calling Tom out for being mean. > >> The CoC is about the later situation and not the prior; and the >> community should call Tom out.

Re: [GENERAL] JSONB performance enhancement for 9.6

Hi, Congrats on the official release of 9.5 And I'd like bring up the issue again about if 9.6 would address the jsonb performance issue with large number of top level keys. It is true that it does not have to use JSON format. it is about serialization and fast retrieval of dynamic tree structure

Re: [GENERAL] Building PostgreSQL in Eclipse on Windows

On Tue, Jan 12, 2016 at 10:32 AM, Igal @ Lucee.org wrote: > I downloaded the PostgreSQL source code and tried to follow the docs but > can't figure out where to download the dependencies? 1. libreadline5-dev, 2. > zlib1g-dev, 3. bison (YACC), 4. flex and where to save them to on disk? Regarding

Re: [GENERAL] WIP: CoC

> That has nothing to do with the Code of Conduct, though. The community > accepting Tom saying "no" to Feature X is vastly different than the community > not calling Tom out for being mean. > The CoC is about the later situation and not the prior; and the community > should call Tom out. (

[GENERAL] plv8 binaries for PostgreSQL 9.5 on Windows

Where can I find binaries for plv8 for PostgreSQL 9.5 for Windows? Thanks, -- Igal Sapir Lucee Core Developer Lucee.org

[GENERAL] Building PostgreSQL in Eclipse on Windows

Can anyone help me figure out how to run/debug PostgreSQL in Eclipse on Windows? This is a cross post with http://stackoverflow.com/questions/34733991/building-postgresql-in-eclipse-on-windows : I'm trying to build|PosgreSQL|in Eclipse CDT Mars on Windows using the MinGW-64 gcc 5.3.0 I ins

Re: [GENERAL] WIP: CoC

On 1/11/2016 4:35 PM, James Keener wrote: To me that's psychological trauma. It's the same psychological trauma I >had to face being born a left-handed and being forced to write with my >right-hand. But it's still not trauma, where is the trauma? Something like Master/Slave to Primary/Replica (

Re: [GENERAL] WIP: CoC

>> 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!) > > Ye

Re: [GENERAL] WIP: CoC V2

On 1/11/2016 6:41 PM, Alban Hertroys wrote: > >> 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, physica

Re: [GENERAL] Offline Tablespaces and Partial Restore

On 1/11/16 8:41 AM, Pedro França wrote: I've tried to put the data on another database but it didn't help as tablespaces are required cluster-wide on startup. If putting the data in a separate database works for you then it wouldn't be a big leap to put it in a separate cluster. Functionality

Re: [GENERAL] Code of Conduct: Is it time?

Steve, Please see the new thread WIP: CoC V2 -- 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 everyone else sh

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] WIP: CoC V2

> 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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] 9.4 -> 9.5 upgrade problem when both python2 and python3 present

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

Re: [GENERAL] Slow Query - PostgreSQL 9.2

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

Re: [GENERAL] WIP: CoC V2

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

Re: [GENERAL] 9.4 -> 9.5 upgrade problem when both python2 and python3 present

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

Re: [GENERAL] WIP: CoC

> """ 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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] Slow Query - PostgreSQL 9.2

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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] WIP: CoC

"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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] WIP: CoC

>> "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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] WIP: CoC

(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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] WIP: CoC

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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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:/

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

> 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

Re: [GENERAL] WIP: CoC

> 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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

[GENERAL] WIP: CoC

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

Re: [GENERAL] Code of Conduct: Is it time?

"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

Re: [GENERAL] Code of Conduct: Is it time? (WIP CoC)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

[GENERAL] Intel Skylake hardware failures

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Slow Query - PostgreSQL 9.2

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;

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct: Is it time?

> 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

Re: [GENERAL] Code of Conduct: Is it time?

"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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Bug Tracker

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:

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Bug Tracker

"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,

[GENERAL]

> 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

Re: [GENERAL] Code of Conduct

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'

[GENERAL] New hacker item posted

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

Re: [GENERAL] Bug Tracker

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

[GENERAL] Bug Tracker

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

Re: [GENERAL] Code of Conduct: Is it time?

> 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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct: Is it time?

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

Re: [GENERAL] Code of Conduct

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

Re: [GENERAL] Code of Conduct: Is it time?

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

[GENERAL] Code of Conduct

Maybe Trump should write this

Re: [GENERAL] Code of Conduct: Is it time?

> 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

Re: [GENERAL] Code of Conduct: Is it time?

>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

Re: Things to notice (was Re: [GENERAL] Code of Conduct: Is it time?, broken thread I hope)

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

Re: [GENERAL] Code of Conduct: Is it time?

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

  1   2   >