Re: Code of Conduct plan

On Wed, Jun 6, 2018 at 2:07 AM, Jan Claeys wrote: > On Tue, 2018-06-05 at 16:45 +0200, Chris Travers wrote: > > If I may suggest: The committee should be international as well > > and include people from around the world. The last thing we want is > > for it to be dominated by people from one

Re: limit and query planner

On 6 June 2018 at 07:17, armand pirvu wrote: > So since > select count(*) from sp_i2birst_reg_staging_test; > count > --- > 6860 > and > select count(*) from sp_i2birst_reg_staging_test where evt_id = 'ACSF17' > and status=0 ; > count > --- > 4239 > > That means to me I fetch almost the

Re: Code of Conduct plan

Adrian Klaver writes: > On 06/05/2018 04:41 PM, Tom Lane wrote: >> I'm getting a little tired of people raising hypothetical harms and >> ignoring the real harms that we're hoping to fix. Yes, this is an >> experiment and it may not work, but we can't find out without trying. >> If it turns out

Re: Code of Conduct plan

I have always been impressed with the core team's and posters' professionalism on this forum. I think the subject matter is vastly responsible for that, actuall and a natural filter for the people and the actual posts. But I also give this compliment  to all of you as individuals. Apparently we

Re: Code of Conduct plan

On 06/05/2018 04:41 PM, Tom Lane wrote: Benjamin Scherrey writes: On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: Not at all. The need for a CoC is not theoretical. Real people, recently, have left the community due to harassment, and there was no system within the community to

Re: ERROR: found multixact from before relminmxid

Em seg, 28 de mai de 2018 às 16:44, Andres Freund escreveu: > > Hi, > > I think I found the bug, and am about to post a fix for it belo > https://postgr.es/m/20180525203736.crkbg36muzxrj...@alap3.anarazel.de. > > Greetings, > > Andres Freund Hi Andres, In end of April we did a complete

Re: pg_stats avg_width and null_frac

On Tue, Jun 5, 2018 at 5:49 PM, Paul McGarry wrote: > Can anyone confirm that the "avg_width" reported in the pg_stats is the > avg_width not including any null rows? > ​Yes. https://github.com/postgres/postgres/blob/master/src/include/catalog/pg_statistic.h#L40 It actually is documented but

pg_stats avg_width and null_frac

Can anyone confirm that the "avg_width" reported in the pg_stats is the avg_width not including any null rows? ie if a field had: avg_width: 6 null_frac: 0.5 Then - 50% of the rows would be empty for this field - The other 50% of the rows would have data with an avg_width of 6 bytes? (according

Re: Segfault leading to crash, recovery mode, and TOAST corruption

Thank you so very much, Tom. Vacuuming fixed the TOAST corruption issue and we’ll upgrade our instances tonight (max RDS has is 10.3, but that’s a start). > On Jun 5, 2018, at 8:07 PM, Tom Lane wrote: > > Jonathan Marks writes: >> We had two issues today (once this morning and once a few

Re: Code of Conduct plan

> On Jun 5, 2018, at 17:07, Jan Claeys wrote: > > For example: having some people who have a background in something like > psychology, sociology, education, law, human resources, marketing, etc. > (in addition to the likely much easier to find developers, DBAs and IT > managers) would be

Re: Code of Conduct plan

On 06/05/2018 05:07 PM, Jan Claeys wrote: On Tue, 2018-06-05 at 16:45 +0200, Chris Travers wrote: If I may suggest: The committee should be international as well and include people from around the world. The last thing we want is for it to be dominated by people from one particular cultural

Re: Pgagent is not reading pgpass file either in Windows or Linux.

On 06/05/2018 07:53 AM, nageswara Bandla wrote: Adrian, I think, it's not problem with pg_hba.conf.  /etc/hosts is configured correctly. psql works fine and is inline with libpq, where as pgagent is not. pgagent still fails when we use hostaddr and host. usr/bin/pgagent_96 -f -l 2

Re: Segfault leading to crash, recovery mode, and TOAST corruption

Jonathan Marks writes: > We had two issues today (once this morning and once a few minutes ago) > with our primary database (RDS running 10.1, 32 cores, 240 GB RAM, 5TB > total disk space, 20k PIOPS) where the database suddenly crashed and > went into recovery mode. I'd suggest updating to 10.4

Re: Code of Conduct plan

On Tue, 2018-06-05 at 16:45 +0200, Chris Travers wrote: > If I may suggest: The committee should be international as well > and include people from around the world. The last thing we want is > for it to be dominated by people from one particular cultural > viewpoint. Being

Re: What specific circumstances trigger Autovacuum wraparound

Hello David! Thanks for taking the time to respond. Upgrading is not in scope right now for this server even though that is certainly something I will do down the line. I talked to a colleague of mine and he dug up something very interesting and probably answers the behavior I'm seeing, from PG

Re: Code of Conduct plan

On 06/05/2018 04:41 PM, Tom Lane wrote: Benjamin Scherrey writes: On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: Not at all. The need for a CoC is not theoretical. Real people, recently, have left the community due to harassment, and there was no system within the community to

Re: Which backend using which pg_temp_N schema?

Adrian Klaver writes: > On 06/05/2018 02:53 PM, Jerry Sievers wrote: > >> Was just studying a legacy DB to learn about temp table activity. >> >> Felt like being able to tie temp schemas to live backends s/b useful but >> then didn't find a function/view for doing this. > > I don't understand

Re: Code of Conduct plan

Benjamin Scherrey writes: > On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: >> Not at all. The need for a CoC is not theoretical. Real people, >> recently, have left the community due to harassment, and there was no >> system within the community to report and deal with that

Re: Code of Conduct plan

On 5 June 2018 at 17:34, Ozz Nixon wrote: > Sorry... > > > 1) CoC might result in developers leaving projects > > > I know this on going regurgitation is going to cause my team to > leave the project, right around 100 posts on this off topic topic it > was bad enough when the

Segfault leading to crash, recovery mode, and TOAST corruption

Hello — We had two issues today (once this morning and once a few minutes ago) with our primary database (RDS running 10.1, 32 cores, 240 GB RAM, 5TB total disk space, 20k PIOPS) where the database suddenly crashed and went into recovery mode. The first time this happened, we restarted the

Re: Which backend using which pg_temp_N schema?

On 06/05/2018 02:53 PM, Jerry Sievers wrote: Was just studying a legacy DB to learn about temp table activity. Felt like being able to tie temp schemas to live backends s/b useful but then didn't find a function/view for doing this. I don't understand what the above is getting at. Can you

Re: Code of Conduct plan

> On Jun 5, 2018, at 15:20, Peter Geoghegan wrote: > I don't follow. Practically any organized group has rules around > conduct, with varying degrees of formality, means of enforcement, etc. I believe the objection is to setting up a separate CoC committee, rather than using the core team as

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 2:06 PM, Sven R. Kunze wrote: > 1) CoC might result in developers leaving projects > http://lists.llvm.org/pipermail/llvm-dev/2018-May/122922.html This guy left LLVM for several reasons. The pertinent reason for us was that he had to agree to a code of conduct in order to

Which backend using which pg_temp_N schema?

Was just studying a legacy DB to learn about temp table activity. Felt like being able to tie temp schemas to live backends s/b useful but then didn't find a function/view for doing this. A quic \df for functions with names likely to be fruitful revealed nothing. Did likewise for sysinfo views.

Re: Reset the cursor to start from the record 1

On Tue, Jun 5, 2018 at 2:08 PM, Igor Korot wrote: > Is there a function which just reset the record pointer to 1, so I can > reprocess > those records > ​? > ​While I haven't actually programmed using this API... The documentation doesn't seem to indicate the presence of a "record pointer", it

RE: Code of Conduct plan

Sorry... > 1) CoC might result in developers leaving projects I know this on going regurgitation is going to cause my team to leave the project, right around 100 posts on this off topic topic it was bad enough when the original idea came up (2 years ago I think). It used to be

Reset the cursor to start from the record 1

Hi, ALL, I'd like to do the following: [code] PGresult res = PQprepare(); if( PQresultStatus( res ) != PGRES_COMMAND_OK ) { // error handling } else { PGresult res1 = PQexecPrepared(); status = PQresultStatus( res1 ); if( status != PGRES_COMMAND_OK && status != PGRES_TUPLES_OK )

Re: Code of Conduct plan

Hi PostgreSQL Community, some points I like to make mainly because of observations of how other open source projects handle this topic: 1) CoC might result in developers leaving projects http://lists.llvm.org/pipermail/llvm-dev/2018-May/122922.html 2) CoC might result in not so equal peers

Re: Code of Conduct plan

> On Jun 5, 2018, at 3:16 PM, Tom Lane wrote: > > Chris Travers writes: >> On Tue, Jun 5, 2018 at 8:42 PM, James Keener wrote: >>> The question is: how can you (honestly) make people feel like we'll take >>> complaints seriously, while also not allowing for the politics that I've >>> seen

Re: Code of Conduct plan

On 06/05/2018 12:12 PM, Christophe Pettus wrote: On Jun 5, 2018, at 12:06, Benjamin Scherrey wrote: Doesn't that 20 years of results pretty clearly demonstrate that this community does not gain an advantage for adopting a CoC? Not at all. The need for a CoC is not theoretical. Real

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 12:20 PM, Benjamin Scherrey wrote: > I keep hearing this claim. I've followed up and tried to verify them. Sorry > but "trust me" doesn't cut it here any more than "trust me this will make > Postgres go faster" would on a code change. What's the context for this? > What

Re: Code of Conduct plan

> On Jun 5, 2018, at 12:20, Benjamin Scherrey wrote: > I'm not trying to harp on you personally, it's just that you're the unlucky > umpteenth time I've seen this claim made with zero satisfaction. Given that we are talking about human beings here, who (unlike code commits) have careers and

Re: Code of Conduct plan

Hi, On 2018-06-06 02:20:45 +0700, Benjamin Scherrey wrote: > On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: > > > > > > On Jun 5, 2018, at 12:06, Benjamin Scherrey > > wrote: > > > Doesn't that 20 years of results pretty clearly demonstrate that this > > community does not gain an

Re: Code of Conduct plan

Greetings, * Benjamin Scherrey (scher...@proteus-tech.com) wrote: > On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: > > Not at all. The need for a CoC is not theoretical. Real people, > > recently, have left the community due to harassment, and there was no > > system within the

Re: Code of Conduct plan

On Wed, Jun 6, 2018 at 2:12 AM, Christophe Pettus wrote: > > > On Jun 5, 2018, at 12:06, Benjamin Scherrey > wrote: > > Doesn't that 20 years of results pretty clearly demonstrate that this > community does not gain an advantage for adopting a CoC? > > Not at all. The need for a CoC is not

Re: limit and query planner

> On Jun 5, 2018, at 2:02 PM, Tom Lane wrote: > > armand pirvu writes: >> My question is: I suspect the limit simply limits the fethching to the first >> n-records retrieved and has no implications whatsoever on the planner, >> meaning the planner ignores it. Am I right or wrong ? > >

Re: Code of Conduct plan

Chris Travers writes: > On Tue, Jun 5, 2018 at 8:42 PM, James Keener wrote: >> The question is: how can you (honestly) make people feel like we'll take >> complaints seriously, while also not allowing for the politics that I've >> seen surround recent incarnations of Codes of Conduct? > At the

Re: Code of Conduct plan

> On Jun 5, 2018, at 12:06, Benjamin Scherrey wrote: > Doesn't that 20 years of results pretty clearly demonstrate that this > community does not gain an advantage for adopting a CoC? Not at all. The need for a CoC is not theoretical. Real people, recently, have left the community due to

Re: Code of Conduct plan

On Wed, Jun 6, 2018 at 12:36 AM, Joshua D. Drake wrote: > On 06/05/2018 10:26 AM, Chris Travers wrote: > > Let's role play. I'll be a homophobic person. >> >> You've just submitted a proposal suggesting that we change >> master-master replication to be multi-partner replication. I've

Re: limit and query planner

armand pirvu writes: > My question is: I suspect the limit simply limits the fethching to the first > n-records retrieved and has no implications whatsoever on the planner, > meaning the planner ignores it. Am I right or wrong ? You're quite wrong. The presence of a LIMIT causes the planner

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 8:42 PM, James Keener wrote: > I accidentally didn't send this to the whole list. I'll let Chris resend > his response if he'd like. > > On Tue, Jun 5, 2018 at 1:58 PM, James Keener wrote: > >> I think the fundamental outcome is likely to be that people who cause >>>

Re: Code of Conduct plan

I accidentally didn't send this to the whole list. I'll let Chris resend his response if he'd like. On Tue, Jun 5, 2018 at 1:58 PM, James Keener wrote: > I think the fundamental outcome is likely to be that people who cause >> trouble are likely to get trouble. This sort of case really

Re: Code of Conduct plan

> On Jun 5, 2018, at 08:49, Benjamin Scherrey wrote: > I thought the same thing as a member of the Django community. It adopted a > CoC that I vocally warned was dangerous and far more likely to be abused than > provide any benefit. I was shocked when the very first time it was ever >

Re: limit and query planner

> On Jun 5, 2018, at 1:32 PM, Pavel Stehule wrote: > > > > 2018-06-05 20:24 GMT+02:00 armand pirvu >: > All > > Please see below > > explain analyze select * from sp_i2birst_reg_staging_test where evt_id = > 'ACSF17' > and status=0 limit 10; >

Re: limit and query planner

2018-06-05 20:24 GMT+02:00 armand pirvu : > All > > Please see below > > explain analyze select * from sp_i2birst_reg_staging_test where evt_id = > 'ACSF17' > and status=0 limit 10; > QUERY PLAN > >

limit and query planner

All Please see below explain analyze select * from sp_i2birst_reg_staging_test where evt_id = 'ACSF17' and status=0 limit 10; QUERY PLAN

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 10:08 AM, Tom Lane wrote: > So publishing a formal CoC at all is mainly meant to deal with weak > points 1 and 2, and then the details of the process are there to try > to fix point 3. > > Yeah, managing the committee is a lot of overhead that in an ideal > world we

Re: Code of Conduct plan

Greetings, * Magnus Hagander (mag...@hagander.net) wrote: > On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers > wrote: > > If I may suggest: The committee should be international as well and > > include people from around the world. The last thing we want is for it to > > be dominated by people

Re: Code of Conduct plan

On 06/05/2018 10:44 AM, James Keener wrote: Your example is flawed because: Multi-Partner has nothing to do with sexuality unless you want to make the argument that your belief is that a relationship should be between one person and another and in this argument a man and a

Re: Code of Conduct plan

> Your example is flawed because: > > Multi-Partner has nothing to do with sexuality unless you want to make the > argument that your belief is that a relationship should be between one > person and another and in this argument a man and a woman which has > literally nothing to do with the word

Re: Code of Conduct plan

On 06/05/2018 10:26 AM, Chris Travers wrote: Let's role play. I'll be a homophobic person. You've just submitted a proposal suggesting that we change master-master replication to be multi-partner replication. I've told you I don't like the wording because of it's implication of

Failover replication building a new master

I am using Postgres 10.4, and using replication, I have managed to set up four servers, with one running as a master and the other three running with streaming replication from the master. I have used the command: psql -c "ALTER SYSTEM SET synchronous_standby_names TO 'FIRST 1(S2,S3,S4)';"

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 7:01 PM, James Keener wrote: > I'm sorry for the double post. > > > If you read the reporting guidelines, it is requested that someone > filing a > report provides as much evidence as possible, and that is a really > important provision, both for the person reporting and

Re: Code of Conduct plan

"David G. Johnston" writes: > Tangential, are there plans to increase number of core team members. IIRC > its actually decreased by one between the time of the first proposal of the > CoC and now. We're thinking about it, but it's not something to be hasty over. > As an outside observer I am a

Re: Code of Conduct plan

On Wed, Jun 6, 2018 at 12:01 AM, James Keener wrote: > I'm sorry for the double post. > > > If you read the reporting guidelines, it is requested that someone > filing a > report provides as much evidence as possible, and that is a really > important provision, both for the person reporting and

Re: Code of Conduct plan

I'm sorry for the double post. > If you read the reporting guidelines, it is requested that someone filing a report provides as much evidence as possible, and that is a really important provision, both for the person reporting and for the committee to review and adjudicate fairly. What does

Re: Code of Conduct plan

> On Jun 5, 2018, at 9:51 AM, James Keener wrote: > > > [T]he > main goal is to ensure that if someone is being harassed by a community > member, they have an appropriate avenue to safely report it and ensure > the CoC committee will review > > To be honest, this is a bigger problem. Why

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 9:51 AM, James Keener wrote: > To be honest, this is a bigger problem. Why would someone not feel > comfortable contacting the core team? Why would they feel better contacting > the CoC board who is probably mostly core team or otherwise self-selected > community members

Re: Code of Conduct plan

James Keener writes: > I also think that a CoC focuses on the wrong things. If someone is > disruptive, they need to be told to leave, just like in every forum ever. That's pretty much what the CoC *is*: it's just trying to set out an agreed-on framework for exercising the power to ban

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 9:32 AM, Tom Lane wrote: > Yeah, personally I'm a bit worried about this too. The proposed CoC > does contain provisions to try to prevent misusing it, but whether those > are strong enough remains to be seen --- and it'll depend a good deal > on the judgment of the

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 6:21 PM, James Keener wrote: > I also think that a CoC focuses on the wrong things. If someone is > disruptive, they need to be told to leave, just like in every forum ever. > > We should focus on ensuring that the code and documentation is free from > slurs and culturally

Re: Code of Conduct plan

> [T]he main goal is to ensure that if someone is being harassed by a community member, they have an appropriate avenue to safely report it and ensure the CoC committee will review To be honest, this is a bigger problem. Why would someone not feel comfortable contacting the core team? Why would

Re: Code of Conduct plan

On June 5, 2018 12:36:37 PM EDT, "Joshua D. Drake" wrote: >On 06/05/2018 09:32 AM, Tom Lane wrote: >> James Keener writes: >>> I don't participate too much here, but I've never see a group >implement >>> a code of conduct go well. >> >> Yeah, personally I'm a bit worried about this too.

Re: Code of Conduct plan

> On Jun 5, 2018, at 12:32 PM, Tom Lane wrote: > > James Keener writes: >> I don't participate too much here, but I've never see a group implement >> a code of conduct go well. There’s also a lot of evidence to the contrary, where groups have successfully implemented CoCs as well by

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 11:36 PM, Joshua D. Drake wrote: > On 06/05/2018 09:32 AM, Tom Lane wrote: > >> James Keener writes: >> >>> I don't participate too much here, but I've never see a group implement >>> a code of conduct go well. >>> >> >> Yeah, personally I'm a bit worried about this too.

Re: Code of Conduct plan

On 06/05/2018 09:32 AM, Tom Lane wrote: James Keener writes: I don't participate too much here, but I've never see a group implement a code of conduct go well. Yeah, personally I'm a bit worried about this too. The proposed CoC does contain provisions to try to prevent misusing it, but

Re: Code of Conduct plan

James Keener writes: > Do we need a code of conduct like this, or so we need a more general > dispute resolution process? We haven't really had many "disputes" in general, so I'm not sure why you feel that something else is needed. In any case, given that not everyone is even happy with the

Re: Code of Conduct plan

> Nobody is claiming that the CoC is perfect, or that it can anticipate every situation; it's just a framework for handling disputes about abusive and/or antisocial behavior 1) Antisocial is a cop-outs word that is so broad as to be useless. That previous sentence can be classified as antisocial

Re: Code of Conduct plan

I also think that a CoC focuses on the wrong things. If someone is disruptive, they need to be told to leave, just like in every forum ever. We should focus on ensuring that the code and documentation is free from slurs and culturally specific idioms. We should hold gatekeepers accountable for

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 8:49 AM, Benjamin Scherrey wrote: > I thought the same thing as a member of the Django community. It adopted a > CoC that I vocally warned was dangerous and far more likely to be abused > than provide any benefit. I was shocked when the very first time it was ever > invoked

Re: Code of Conduct plan

Do we need a code of conduct like this, or so we need a more general dispute resolution process? Something that is public and aimed at mediating disputes (even ones about bad conduct) and removing repeat offenders. To be honest, larger issues of harassment should be handled by the police. A

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers wrote: > > > On Mon, Jun 4, 2018 at 6:59 PM, Joshua D. Drake > wrote: > >> On 06/03/2018 04:08 PM, Gavin Flower wrote: >> >> My comments: 1) Reiterate my contention that this is a solution is search of problem. Still it looks like it

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 10:48 PM, Joshua D. Drake wrote: > On 06/05/2018 08:41 AM, Lutz Horn wrote: > >> Am 05.06.2018 17:26 schrieb Joshua D. Drake: >> >>> As one of the people that interacts with external members of the >>> community more than most, I can tell you that a CoC is something the

Re: Code of Conduct plan

On Tue, 5 Jun 2018 at 01:18, Tom Lane wrote: > I think you're forgetting the sequence of events. That was posted in > Feb 2016. In May 2016 we posted a draft CoC which was open for public > discussion, and was discussed extensively at a public meeting at PGCon > in that same month [1], and the

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 10:37 PM, Peter Geoghegan wrote: > It is of course possible that a member of the committee could act in > bad faith for any number of reasons. You can say the same thing about > any position of leadership or authority within the community, though. > That hasn't really been

Re: Code of Conduct plan

On 06/05/2018 08:41 AM, Lutz Horn wrote: Am 05.06.2018 17:26 schrieb Joshua D. Drake: As one of the people that interacts with external members of the community more than most, I can tell you that a CoC is something the wider community wants. I have sat in feedback meetings with hundreds of

Re: Code of Conduct plan

Am 05.06.2018 17:26 schrieb Joshua D. Drake: As one of the people that interacts with external members of the community more than most, I can tell you that a CoC is something the wider community wants. I have sat in feedback meetings with hundreds of people who are potential community members.

Re: [MASSMAIL]Re: Code of Conduct plan

O.K, Remember my Country Please. El 2018-06-05 11:29, Joshua D. Drake escribió: On 06/05/2018 07:45 AM, Chris Travers wrote: It is my hope that PostgreSQL.Org -Core chooses members for that committee that are exceedingly diverse otherwise it is just an echo chamber for a

Re: Code of Conduct plan

Am 05.06.2018 17:33 schrieb Joshua D. Drake: Let's remember that we are an International project and let's not direct particular frustration at any particular set of values. It would be very easy to start a culture war within this thread alone. I am not quite sure what you mean by "particular

Re: Code of Conduct plan

On Mon, Jun 4, 2018 at 11:41 AM, Jason Petersen wrote: > Ultimately, the important thing this CoC provides is some concrete language > to point at when a party is aggrieved and explicit avenues of redress > available when one refuses to address one’s own behavior. We’re adults here, > the

Re: Code of Conduct plan

On 06/05/2018 08:19 AM, Lutz Horn wrote: Am 05.06.2018 17:03 schrieb Chris Travers: On to the code of conduct committee: This needs to be explicitly international and ideally people from very different cultures.  This is the best protection against one small group within one country deciding

Re: Code of Conduct plan

On 06/05/2018 07:45 AM, Chris Travers wrote: It is my hope that PostgreSQL.Org -Core chooses members for that committee that are exceedingly diverse otherwise it is just an echo chamber for a single ideology and that will destroy this community. If I may suggest:  The committee

Re: Code of Conduct plan

On 06/04/2018 09:55 PM, Tom Lane wrote: Adrian Klaver writes: On 06/03/2018 11:29 AM, Tom Lane wrote: https://wiki.postgresql.org/wiki/Code_of_Conduct We are now asking for a final round of community comments. My comments: 1) Reiterate my contention that this is a solution is search of

Re: Code of Conduct plan

Am 05.06.2018 17:03 schrieb Chris Travers: On to the code of conduct committee: This needs to be explicitly international and ideally people from very different cultures. This is the best protection against one small group within one country deciding to push a political agenda via the Code

Re: Code of Conduct plan

On Sun, Jun 3, 2018 at 8:29 PM, Tom Lane wrote: > Two years ago, there was considerable discussion about creating a > Code of Conduct for the Postgres community, as a result of which > the core team announced a plan to create an exploration committee > to draft a CoC [1]. That process has taken

Re: Sort is generating rows

Hi, I've tried some tests, by generating various datas in the res_currency_rate table. If I generate res_currency_rate rows for unsused currencies, this doesn't influence the execution time. if I generate more res_currency_rate for used currencies, this slower the query. If I generate 100 rates,

Re: [MASSMAIL]Re: Code of Conduct plan

El 2018-06-05 10:54, gilberto.casti...@etecsa.cu escribió: Hello, Maybe must include policy of money support from several at member from country less earnings. El 2018-06-05 10:45, Chris Travers escribió: On Mon, Jun 4, 2018 at 6:59 PM, Joshua D. Drake wrote: On 06/03/2018 04:08 PM, Gavin

Re: [MASSMAIL]Re: Code of Conduct plan

Hello, Maybe must include policy of money support from several at member from country less earnings. For examplo Cuba. El 2018-06-05 10:45, Chris Travers escribió: On Mon, Jun 4, 2018 at 6:59 PM, Joshua D. Drake wrote: On 06/03/2018 04:08 PM, Gavin Flower wrote: My comments: 1)

Re: Pgagent is not reading pgpass file either in Windows or Linux.

Adrian, I think, it's not problem with pg_hba.conf. /etc/hosts is configured correctly. psql works fine and is inline with libpq, where as pgagent is not. pgagent still fails when we use hostaddr and host. usr/bin/pgagent_96 -f -l 2 hostaddr=127.0.0.1 host=localhost dbname=linuxpostgresdb

Re: Code of Conduct plan

On Mon, Jun 4, 2018 at 6:59 PM, Joshua D. Drake wrote: > On 06/03/2018 04:08 PM, Gavin Flower wrote: > > My comments: >>> >>> 1) Reiterate my contention that this is a solution is search of problem. >>> Still it looks like it is going forward, so see below. >>> >>> 2) "... engaging in behavior

Re: Sort is generating rows

Hi, you're right, I've also changed the lateral join. The lateral join remove the row generation, and use a loop. I've remove the lateral join, on the same dataset as the one used for provided explain plan, and time to execute grows up to 18s: SELECT min(l.id) AS id, l.product_id,

Re: Postgres 11 beta - no JITing

Andres Freund schrieb am 05.06.2018 um 14:34: >> I am trying to assess the benefits of the new JIT feature in Postgres 11. >> However I can't figure out how to enable it. >> >> I have a test server with "CentOS Linux release 7.5.1804" >> >> I installed the beta using: >> >> yum install >>

Re: Postgres 11 beta - no JITing

Hi, On 2018-06-05 13:45:26 +0200, Thomas Kellerer wrote: > Hello, > > I am trying to assess the benefits of the new JIT feature in Postgres 11. > However I can't figure out how to enable it. > > I have a test server with "CentOS Linux release 7.5.1804" > > I installed the beta using: > >

Postgres 11 beta - no JITing

Hello, I am trying to assess the benefits of the new JIT feature in Postgres 11. However I can't figure out how to enable it. I have a test server with "CentOS Linux release 7.5.1804" I installed the beta using: yum install

Re: How to get postmaster shut down time in postgres?

Hi Tom Lane, I'm glad that I got a reply from you. And yes you are exactly correct. I am looking for the time that shutdown begins. I fulfilled my requirement by adding a piece of code before the initiation of shutdown in the postgresql service file located in /etc/init.d folder of my ubuntu

Re: How to get postmaster shut down time in postgres?

Hi Tom Lane, I'm glad that I got a reply from you. And yes you are exactly correct. I am looking for the time that shutdown begins. I fulfilled my requirement by adding a piece of code before the initiation of shutdown in the postgresql service file located in /etc/init.d folder of my ubuntu

Re: How to get postmaster shut down time in postgres?

Hi Tom Lane, I'm glad that I got a reply from you. And yes you are exactly correct. I am looking for the time that shutdown begins. I fulfilled my requirement by adding a piece of code before the initiation of shutdown in the postgresql service file located in /etc/init.d folder of my ubuntu