Re: [GENERAL] Statement timeout

On 01/29/2016 07:00 AM, Edson Richter wrote: I've set statement timeout in postgresql.conf to 300s. Now, I have a schema update procedure at application startup I would like to run without timeout, or with significant larger timeout (let's say, 1s). It is possible to change statement

Re: [GENERAL] pg_dump streaming fails - PostgreSQL 9.2

On 01/28/2016 05:23 PM, drum.lu...@gmail.com wrote: Hi there! I'm running this command: *(Trying to copy a full DB (2TB) from a hot-standby server to a master (test) server)* |ssh postgres@myslaveserver "/usr/pgsql-9.2/bin/pg_dump --exclude-table-data='junk.*' -—format=custom

Re: [GENERAL] BRIN indexes

On 01/28/2016 09:41 AM, Melvin Davidson wrote: So, IOW, and the answer to my question is yes, it should be insured that all pages involved are physically adjacent (by design or by pre-sort) before creating a BRIN on them. Further to the point, it is self defeating to have more than one BRIN

Re: [GENERAL] Catalog bloat (again)

On 01/27/2016 03:37 PM, Ivan Voras wrote: On 28 January 2016 at 00:13, Bill Moran > wrote: On Wed, 27 Jan 2016 23:54:37 +0100 Ivan Voras > wrote: > So, question #1: WTF? How

Re: [GENERAL] Catalog bloat (again)

On 01/27/2016 03:37 PM, Ivan Voras wrote: On 28 January 2016 at 00:13, Bill Moran > wrote: On Wed, 27 Jan 2016 23:54:37 +0100 Ivan Voras > wrote: > So, question #1: WTF? How

Re: [GENERAL] CoC [Final v2]

On 01/26/2016 09:03 AM, Jan Danielsson wrote: On 24/01/16 18:30, Joshua D. Drake wrote: Hello, This thread is deprecated. The CoC Final Draft has been submitted to -core for final modification, acceptance or decline. Sincerely, Joshua D. Drake -- Command Prompt, Inc

Re: [GENERAL] Tutorial on How to Compile PostgreSQL 9.5 for Windows 64bit

On 01/25/2016 10:49 AM, Joshua Berkus wrote: - Original Message - Hi Everybody, I have posted a video tutorial on How to Compile PostgreSQL 9.5 for Windows 64bit https://www.youtube.com/watch?v=-BJmuZT5IPE It was quite difficult for me to figure it out, so hopefully it will make

Re: [GENERAL] CoC [Final v2]

Hello, This thread is deprecated. The CoC Final Draft has been submitted to -core for final modification, acceptance or decline. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full

Re: [GENERAL] A motion

Hello, This thread is deprecated. The CoC Final Draft has been submitted to -core for final modification, acceptance or decline. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full

Re: [GENERAL] Tutorial on How to Compile PostgreSQL 9.5 for Windows 64bit

On 01/25/2016 05:29 PM, Michael Paquier wrote: On Tue, Jan 26, 2016 at 3:56 AM, Joshua D. Drake <j...@commandprompt.com> wrote: On 01/25/2016 10:49 AM, Joshua Berkus wrote: - Original Message - Hi Everybody, I have posted a video tutorial on How to Compile PostgreS

Re: [GENERAL] request for comment re "contributor-covenant.org"

Zenaan, Thank you for providing your insight. However, our Core Committee is already considering a CoC and is in final stages of either modification, acceptance or decline. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company

Re: [GENERAL] Possible to dump/load a database from within psql?

On 01/25/2016 02:16 AM, Brian Cardarella wrote: Is it possible, and if so how, to dump and then load a database to/from a file from within a psql connection? pg_dump -h $host -U $user $database|psql -U $user -h $host $database http://www.postgresql.org/docs/9.5/static/app-pgdump.html

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 02:42 PM, David E. Wheeler wrote: How do you define “in the Pg community”? Is it someone who has posted to a known forum at least once? Someone who has been to a conference? What if they have never participated in a community forum, but use PostgreSQL at work? Maybe they would

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 02:41 PM, Christophe Pettus wrote: On Jan 22, 2016, at 6:47 PM, Joshua D. Drake <j...@commandprompt.com> wrote: == PostgreSQL Community Code of Conduct (CoC) == What is missing from this, first and foremost, is a reporting and resolution mechanism. If someone feels t

Re: [GENERAL] CoC [Final v2]

of the existing CoC Final Draft that you do not like or would like to see changed? Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. -- Se

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 02:42 PM, David E. Wheeler wrote: 1. If person B is not in the Pg community then it is up to the Rails community to deal with it. 2. If person B is in the Pg community they can request help. I am open to wording on #2. I tried a couple of times but had trouble not making it a

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 05:20 PM, Christophe Pettus wrote: On Jan 24, 2016, at 5:15 PM, "Joshua D. Drake" <j...@commandprompt.com> wrote: Based on our structure it doesn't work that way. At a minimum we will come up with a CoC and it will be passed to -core for final approval. -core

Re: [GENERAL] CoC [Final v2]

ributors come up with. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 09:39 AM, Geoff Winkless wrote: On 24 January 2016 at 17:30, Joshua D. Drake <j...@commandprompt.com> wrote: Sarcasm is not productive. Actually I wasn't being sarcastic. OK, I was being sarcastic in the first paragraph, but not the second :p The most significant problem

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 09:44 AM, Geoff Winkless wrote: On 24 January 2016 at 17:30, Joshua D. Drake <j...@commandprompt.com> wrote: If you are participating in this thread, be productive. If you are going to be sarcastic and not helpful, get off the thread. And as for being not helpful, I was

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 02:34 AM, Chris Travers wrote: We need to also cover abuse by members of the community made outside the community. Otherwise we’ll appear to give safe harbor to abusers. The private lives of members are the private lives of members. Let whatever

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 07:36 AM, Geoff Winkless wrote: We'll just need you and Dave to sign a legally binding contract that you will provide indemnity for any and all actions that might come about as a result, in all locations worldwide. Oh, and you'll need to pay the legal fees for lawyers (your own

Re: [GENERAL] CoC [Final v2]

On 01/24/2016 08:13 AM, Chris Travers wrote: If I could make one proposal for an additional clause: * PostgreSQL is a community project and takes no position on any political question aside from its usage in the public sector (which we support). We expect communication in community fora to

Re: [GENERAL] CoC [Final v2]

of times but had trouble not making it a larger declaration that I think it needs to be. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. -- Sent

Re: [GENERAL] CoC [Final v2]

) would apply. It would become off-topic. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. -- Sent via pgsql-general mailing list (pgsql-general

Re: [GENERAL] Let's Do the CoC Right

On 01/23/2016 10:07 AM, David E. Wheeler wrote: On Jan 22, 2016, at 6:14 PM, Joshua D. Drake <j...@commandprompt.com> wrote: You can not violate one part of the CoC and use the other part as the reason. You say, that, and yet someone will. Think about law: if laws contradict each

Re: [GENERAL] A motion

On 01/23/2016 03:08 PM, Adrian Klaver wrote: On 01/23/2016 03:03 PM, Berend Tober wrote: Adrian Klaver wrote: Motion: The Coc discussion be moved to its own list where those who care can argue to their hearts content and leave the rest of us to deal with technical questions. Upon a decision

Re: [GENERAL] CoC [Final v2]

On 01/23/2016 04:00 PM, David E. Wheeler wrote: On Jan 22, 2016, at 6:47 PM, Joshua D. Drake <j...@commandprompt.com> wrote: This document provides community guidelines for a safe, respectful, productive, and collaborative place for any person who is willing to contribute to the Post

Re: [GENERAL] A motion

On 01/23/2016 03:40 PM, Andres Freund wrote: On 2016-01-23 15:31:02 -0800, Joshua D. Drake wrote: With respect Adrian, that is a motion that never stands a chance. If you don't want to read it, set up a filter that sends it right to the round file. It'd help if there weren't six, but one

Re: [GENERAL] Let's Do the CoC Right

On 01/23/2016 01:59 PM, Steve Litt wrote: We all need the necessary protection, which is not necessarily equal protection, because some of us are subjected to much more harassment. And I think we all need to walk a mile in other peoples shoes before assuming others need only the meager amount

Re: [GENERAL] Let's Do the CoC Right

On 01/21/2016 11:00 PM, Rajeev Bhatta wrote: Additionally the CoC emails were sent to the entire group so it was open for all. I did not read the remainder of the email as classifying someone by anything is inappropriate. +1 -- Command Prompt, Inc.

Re: [GENERAL] Let's Do the CoC Right

On 01/22/2016 03:31 PM, David E. Wheeler wrote: My own behavior earlier is not a terrible example. By one point on the CoC (“ language and actions are free of personal attacks and disparaging personal remarks”), it seems problematic if not an outright violation. But one can argue by another

Re: [GENERAL] CoC [Final]

On 01/21/2016 12:40 PM, Steve Litt wrote: "Disruption of the collaborative space" is almost meaningless, and almost guarantees selective enforcement. On the other hand, "patterns of behaviour which the majority of the core team consider to be harassment" is crystal clear. What would happen if

[GENERAL] CoC [Final v2]

Hello, I have been in Pasadena the last few days and wasn't able to respond. I believe we are very close to finishing this up. Based on the comments I have seen in the previous CoC [Final] thread, I have come up with the following: == PostgreSQL Community Code of Conduct (CoC) == This

Re: [GENERAL] Question about the postgresql's certifications

On 01/19/2016 12:14 PM, John R Pierce wrote: On 1/15/2016 8:59 AM, Jaime Manuel Padron Cano wrote: Hello, i would like to know what is the difference between the postgresql CE 8 silver and postgresql associate certification which provides EnterpriseDB. Which one is the most recently and which

Re: [GENERAL] Building 9.4 rpm for Red Hat 5

On 01/19/2016 12:21 PM, AI Rumman wrote: Hi All, My production boxes are running on Redhat 5 and I need to build Postgresql 9.4 rpm for it following our environment setup. If I build the rpm on Centos 5, will it be ok to run on Red Hat 5 boxes? Can you please let me know? Thanks. CentOS 5

[GENERAL] CoC [Final]

Hello, O.k. so I let every thing sit with V7 for several days and we have received no further feedback. I believe we have reached a point where we can reasonably consider this Final or at least Final Draft. This final draft incorporates all reasonable feedback I have received as well as

Re: [GENERAL] CoC [Final]

On 01/18/2016 10:15 AM, Kevin Grittner wrote: On Mon, Jan 18, 2016 at 12:02 PM, Joshua D. Drake <j...@commandprompt.com> wrote: * Participants who disrupt the collaborative space, or participate in a pattern of behaviour which could be considered harassment will not be tolerated. Pers

Re: [GENERAL] CoC [Final]

On 01/18/2016 10:38 AM, Karsten Hilbert wrote: On Mon, Jan 18, 2016 at 10:02:33AM -0800, Joshua D. Drake wrote: O.k. so I let every thing sit with V7 for several days and we have received no further feedback. I believe we have reached a point where we can reasonably consider this Final

Re: [GENERAL] WIP: CoC V7

On 01/15/2016 09:03 AM, FarjadFarid(ChkNet) wrote: Joshua and all, Because of the current political environment we live in, even though I am neither a Muslim nor a Jew I am a Baha'i, I think we should not discuss religion or politics on this forum. All such topics can be discussed privately.

[GENERAL] WIP: CoC V7

tl;dr; * Cleaned up first paragraph, making it more succint * Reworded last bullet a bit == PostgreSQL Community Code of Conduct (CoC) == This document provides community guidelines for a safe, respectful, productive, and collaborative place for any person who is willing to contribute to

Re: [GENERAL] WIP: CoC V7

On 01/15/2016 07:41 AM, Joshua D. Drake wrote: tl;dr; * Cleaned up first paragraph, making it more succint * Reworded last bullet a bit == PostgreSQL Community Code of Conduct (CoC) == This document provides community guidelines for a safe, respectful, productive, and collaborative place

Re: [GENERAL] WIP: CoC V5

tl;dr; * added being tolerant of opposing views == PostgreSQL Community Code of Conduct (CoC) == This document is intended 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,

Re: [GENERAL] WIP: CoC V5

On 01/14/2016 09:14 AM, Neil wrote: The community needs to decide between the following: 1. Does it want to eliminate participation from people with strong but opposing views. or 2. Does it want to enforce respect and tolerance that allows people with strong but opposing views to

Re: [GENERAL] WIP: CoC V5, etc., etc., etc., etc., ....

On 01/14/2016 08:30 AM, Adrian Klaver wrote: On 01/14/2016 08:24 AM, Joshua D. Drake wrote: On 01/13/2016 06:00 PM, Berend Tober wrote: Whether or not it is a foregone conclusion that this community will adopt a CoC, it seems like a mailing list is not the place to do revision control. Can

Re: [GENERAL] WIP: CoC V5, etc., etc., etc., etc., ....

On 01/13/2016 06:00 PM, Berend Tober wrote: Whether or not it is a foregone conclusion that this community will adopt a CoC, it seems like a mailing list is not the place to do revision control. Can you people start a github project or something to develope your ideas and come back when you

Re: [GENERAL] WIP: CoC V5

On 01/14/2016 08:53 AM, Geoff Winkless wrote: On 14 January 2016 at 16:37, Joshua D. Drake <j...@commandprompt.com> wrote: If someone stands up in a respectful way in a public place and argues a position, they should not be demonized or punished for that. I completely agree wi

[GENERAL] PgDay LFNW April 23rd & 24th (can you speak?)

Folks, The CFP is open for this, it can be found here: http://linuxfestnorthwest.org/2016/present As usual, we have a dedicated track to PostgreSQL. We however tend to lack topics of the intro variety. It would be great if we could get some folks to submit talks on: PostgreSQL 101: How to

Re: [GENERAL] WIP: CoC V5

Updated. Tl;dr; * Removed excess wording * Removed non-.org controlled spaces in first paragraph * Added explicit discussion on explicit problem with last paragraph of Kevin's last version. == PostgreSQL Community Code of Conduct (CoC) == This document is intended to provide community

Re: [GENERAL] WIP: CoC V6

Hello, I posted this earlier but ended up breaking my own silly rev scheme. So, I am going back to my silly rev scheme. Rev 6 it is: tl;dr; * added being tolerant of opposing views * Removed excess wording from Grittner's version * Removed non-.org controlled spaces in first paragraph ==

Re: [GENERAL] Synchronous replication

On 01/13/2016 12:28 PM, jwienc...@comcast.net wrote: Is it possible to set up synchronous replication to more that one node in a cluster? Or, am I limited to one synchronous node and one asynchronous node? Yes you can have N number of synchronous slaves. However, be careful. It can be a huge

Re: [GENERAL] WIP: CoC V5

On 01/13/2016 01:27 PM, Tom Lane wrote: Steve Litt writes: To me it's simple... Disallow "You " Disallow "Your code " Encourage "It would be better if your code because ." That's fine as practice, but I don't think we want to get anywhere near being that detailed

Re: [GENERAL] WIP: CoC V5

On 01/13/2016 08:05 AM, Tom Lane wrote: My general reaction to the rest of this is that it's got the right idea, but it could be cut to about half the length and be better off for that. Short and sweet is the way, IMO. +1 Less words, more point. -- Command Prompt, Inc. -

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 07:10 PM, Tom Lane wrote: Kevin Grittner writes: I'm not the greatest word-smith, but I'll attempt to rework Josh's draft to something that seems more "natural" to me. Minor (or not?) comment: * To maintain a safe, respectful, productive and collaborative

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 07:04 PM, Tom Lane wrote: "Joshua D. Drake" <j...@commandprompt.com> writes: On 01/12/2016 02:43 PM, Kevin Grittner wrote: To me, this reads more like the document itself. I hope I have done justice to Josh's points as well as Tom's, although I would bet th

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 06:41 PM, Elein wrote: The small problem with your version, Joshua, is that the appropriate action is not specified. Sorry to jump in in the middle. I have not read the comments fully. It is all good Elein. The lack of appropriate action is purposeful. The idea is that we

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 06:55 PM, Tom Lane wrote: Elein writes: The small problem with your version, Joshua, is that the appropriate action is not specified. I think at this point we're just trying to agree on a statement as to what actions are acceptable or not. After that we can

Re: [GENERAL] WIP: CoC

On 01/12/2016 08:17 AM, Neil Tiffin wrote: On Jan 12, 2016, at 12:20 AM, Tom Lane wrote: [ 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

Re: [GENERAL] WIP: CoC V4

On 01/12/2016 12:16 PM, Oleg Bartunov wrote: 4. Any sustained disruption of the collaborative space (mailing lists, IRC etc..) or other PostgreSQL events shall be construed as a violation of the CoC and appropriate action will be taken by the CoC committee. Then we need to

Re: [GENERAL] WIP: CoC V5

tl;dr; * Moved #2 to #3 and #3 to #2 * Added wording for assuming positive intent to #2 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

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 02:43 PM, Kevin Grittner wrote: I think that this is fairly close to something that would make sense, but there is sort of a weirdness in the CoC referring to itself in the 3rd person. It sound more like an argument for *having* a CoC than the document itself. I'm not the

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 02:43 PM, Kevin Grittner wrote: I guess I should scroll all the way down. :P To me, this reads more like the document itself. I hope I have done justice to Josh's points as well as Tom's, although I would bet there are a number of people on the list that can improve on my

Re: [GENERAL] WIP: CoC V4

Tl;dr; * Removed specific examples and reworded #3 to be more concise 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

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.

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

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

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

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

Re: [GENERAL] WIP: CoC

On 01/11/2016 02:54 PM, Tom Lane wrote: "Joshua D. Drake" <j...@commandprompt.com> 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, disa

[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

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

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

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,

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

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,

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.

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

Re: [GENERAL] Bug Tracker

On 01/11/2016 12:07 PM, Tom Lane wrote: "Joshua D. Drake" <j...@commandprompt.com> 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 thre

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

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

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

Hey, For the record, my thoughts on a CoC are something like: 1. Be excellent to each other 2. If you don't know what that means, leave 3. If someone isn't being excellent please contact: XYZ With XYZ being a committee that determines the ABCs. Or in other words something like this (without

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

On 01/10/2016 08:07 AM, Bill Moran wrote: So, the purpose of a CoC is twofold: A) Define what "being excellent" means to this particular community. B) Provide a process for how to resolve things when "being excellent" doesn't happen. Without #1, nobody will want to do #2, as it's

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

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 reasonable but my point is that we don't care if you are sexist (in terms of .Org).

Re: [GENERAL] Support for BDR in 9.5?

On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote: Installed 9.5 to CentOS7 via yum, and tried going through the BDR quick-start guide (minus sections 2.1): http://bdr-project.org/docs/stable/quickstart.html It was unhappy that BDR binaries were not on the path, and failed at section 2.4.

Re: [GENERAL] Packages for Ubuntu Wily

On 01/08/2016 07:35 AM, Adrian Klaver wrote: depend on a package pgdg-keyring , and that package doesn't seem to be available in the " wily-pgdg " distribution in the apt repo. Also, pgadmin3 seems to be missing in that distribution. Am I doing something wrong? Or is this a bug in the

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

On 01/06/2016 09:20 AM, Adrian Klaver wrote: We just have to figure out if it will. (As a cis-hetero white middle class male) I'm not a "targeted" group and as such my views may not be of the most use here. Which is another very good point. Except it is not true. Re: my previous post about

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

On 01/06/2016 08:11 AM, James Keener wrote: The coc sounds like a Washington politics play, but as long as the best still engage in this forum, I could care less. The list serves its purpose without overhead...a rare resource in today's flood of incoherent technical chatter. Beyond "Hey! Look

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

On 01/06/2016 08:13 AM, Jim Nasby wrote: (BTW, if your concern on enforcement is about control, not only can people be removed from mailing lists and the like, but there actually is a Postgres legal entity that could start legal proceedings if it ever came to it.) As a Director for 2 of the

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

On 01/06/2016 02:50 PM, David Gibbons wrote: On 1/6/2016 8:50 AM, Joshua D. Drake wrote: It provides a sense of confidence to those who are not confident that they can come play in our playground and not be bullied. That is what every single code of conduct is about

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

On 01/05/2016 08:56 AM, Melvin Davidson wrote: Joshua, I have to agree that a COC is in order. But to add to that, I would like to see basic requirements when submitting a problem. IE: 1. Version of PostgreSQL 2.. O/S 3. Enough info to duplicate the problem EG: minimal schema & data

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

On 01/05/2016 09:06 AM, Adrian Klaver wrote: Brendan Eich fiasco Has absolutely nothing to do with a CoC. At least from my understanding of what happened. JD -- Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564 PostgreSQL Centered full stack support, consulting and

[GENERAL] Code of Conduct: Is it time?

Hello, I had a hard time writing this email. I think Code of Conducts are non-essential, a waste of respectful people's time and frankly if you are going to be a jerk, our community will call you out on it. Unfortunately a lot of people don't agree with that. I have over the course of the

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

On 01/05/2016 11:08 AM, Roland van Laar wrote: On January 5, 2016 5:47:16 PM GMT+01:00, "Joshua D. Drake" <j...@commandprompt.com> wrote: Hello, I had a hard time writing this email. I think Code of Conducts are non-essential, a waste of respectful people's time and frankly

Re: [GENERAL] Failing to known state

On 01/05/2016 03:21 PM, oleg yusim wrote: Thanks JD. From what I read about WAL (you have been referring to this: http://www.postgresql.org/docs/current/static/wal-internals.html pg_xlog, right?) it allows us to know what happened, but does it warranty known secure state? I mean, I do not

Re: [GENERAL] Failing to known state

On 01/05/2016 03:09 PM, oleg yusim wrote: The question here, what is PostreSQL 9.4.5 (hosted on Linux box) behavior? Does it fail to known/secure state in these 3 cases? I tried to find the description of the way PostgreSQL fails in this regard, but didn't find much. Based on what you

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

On 01/05/2016 05:31 PM, Jim Nasby wrote: Well, that highlights that it's not just about a CoC, it's the things that surround it. Especially what the conflict resolution policy is. I suspect JD thought about this because of a recent Facebook thread[1] about how the FreeBSD community just

Re: [GENERAL] PostgreSQL GUI tools

On 01/03/2016 02:15 AM, subhan alimy wrote: Hello everyone, Is there any PostgreSQL GUI tools to pull the tables structure along with the relationships? A simple Google will show you that there are literally dozens. Much appropriated. -- View this message in context:

[GENERAL] Happy New Year

Welcome to 2016. Let's have another bang up year! -- 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

Re: [GENERAL] HELP!!! The WAL Archive is taking up all space

On 12/09/2015 04:38 PM, FattahRozzaq wrote: Quick information, After I realize, the line "archive_command=/bin/true" is a bad decision, I have revert it back. Now I'm really confused and panic. I don't know what to do, and I don't really understand the postgresql.conf I'm a network engineer, I

Re: [GENERAL] Does PostgreSQL ever create indexes on its own?

On 11/12/2015 02:21 PM, Doiron, Daniel wrote: I’m troubleshooting a schema and found this: Indexes: "pk_patient_diagnoses" PRIMARY KEY, btree (id) "index_4341548" UNIQUE, btree (id) "idx_patient_diagnoses_deleted" btree (deleted) "idx_patient_diagnoses_diagnosis_type_id"

<    1   2   3   4   5   6   7   8   9   10   >