Re: Code of Conduct plan

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 problem. As I mentioned elsewhere,

Re: What specific circumstances trigger Autovacuum wraparound

On Monday, June 4, 2018, Daniel Lagerman wrote: > I have a pg 9.4.3 server that has one table with calculate age of about > 320 million, this is the oldest table in this database and therefore the > age of the DB is the same as the table. > It would be advisable to simply upgrade to 9.4.18 and

Re: Code of Conduct plan

> On Jun 4, 2018, at 7:23 PM, Tom Lane wrote: > > Vik Fearing writes: >> Also I think official text should have its own page on the website, >> rather than just be on the wiki. Hopefully that's already planned. > > Right; we'll mark the formal blessing of the text by moving it onto > the

What specific circumstances trigger Autovacuum wraparound

Hello! Please note that I have read: https://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND And I think i understand how the settings are supposed work, however I do have a question in regards to Autovaccum wrap-around and how it is triggered. I have a pg

Re: Microsoft buys GitHub, is this a threat to open-source

On Mon, Jun 04, 2018 at 08:44:37PM +0200, Pavel Stehule wrote: > I have few projects there - Orafce, plpgsql_check, and pspg. I hope so > these projects are well protected by BSD licence - and distributed > redundant nature of git. I hope so there is not reason for panic this > moment. I have not

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

On 06/04/2018 03:31 PM, nageswara Bandla wrote: I have figured out the issue with pgAgent both in Windows and Linux. PgAgent seems to ignore pgpass.conf/.pgpass whenever it has 127.0.0.1 (127.0.0.1:5432:*:postgres:postgres) throws an error: Could it be that hosts is not set up for?:

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

On 6/4/2018 6:31 PM, nageswara Bandla wrote: I have figured out the issue with pgAgent both in Windows and Linux. PgAgent seems to ignore pgpass.conf/.pgpass whenever it has 127.0.0.1 (127.0.0.1:5432:*:postgres:postgres) throws an error: *DEBUG: Creating DB connection: user=postgres

Re: Code of Conduct plan

Geoff Winkless writes: > On Sun, 3 Jun 2018 at 22:47, Tom Lane wrote: >> In any case, we went over all these sorts of arguments at excruciating >> length in 2016. It's quite clear to the core team that a majority of >> the community wants a CoC. I don't think any useful purpose will be >>

Re: Code of Conduct plan

Vik Fearing writes: > Also I think official text should have its own page on the website, > rather than just be on the wiki. Hopefully that's already planned. Right; we'll mark the formal blessing of the text by moving it onto the main website. The translated versions should end up there too.

Re: Code of Conduct plan

On 05/06/18 01:07, Tom Lane wrote: > Tatsuo Ishii writes: >>> https://wiki.postgresql.org/wiki/Code_of_Conduct > >> Do we want official translations of this? We allow local communities >> do their own manual translations. However CoC is so important, I feel >> like we need more for Coc. Good

Re: Code of Conduct plan

>> Do we want official translations of this? We allow local communities >> do their own manual translations. However CoC is so important, I feel >> like we need more for Coc. Good thing with CoC is, it is expected that >> it would be stable (at least I hope so) and translation works when >> it's

Re: Code of Conduct plan

Tatsuo Ishii writes: >> https://wiki.postgresql.org/wiki/Code_of_Conduct > Do we want official translations of this? We allow local communities > do their own manual translations. However CoC is so important, I feel > like we need more for Coc. Good thing with CoC is, it is expected that > it

Re: Code of Conduct plan

> On Jun 4, 2018, at 6:41 PM, Tom Lane wrote: > > "Joshua D. Drake" writes: >> On 06/04/2018 01:46 PM, Tom Lane wrote: >>> ... The reason for this is an unfortunate situation that took place in >>> the FreeBSD community awhile back [1], wherein one community member was >>> abusing another via

Re: Code of Conduct plan

> On Jun 4, 2018, at 3:30 PM, Joshua D. Drake wrote: > > On 06/04/2018 01:46 PM, Tom Lane wrote: >> "Joshua D. Drake" writes: >>> On 06/03/2018 11:29 AM, Tom Lane wrote: We are now asking for a final round of community comments. >> Actually, it's intentional that we are not saying that.

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

I've noticed that .pgpass is case sensitive, so am not surprised that it also wouldn't note the difference between 127.0.0.1 and localhost. On 06/04/2018 05:31 PM, nageswara Bandla wrote: I have figured out the issue with pgAgent both in Windows and Linux. PgAgent seems to ignore

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

I have figured out the issue with pgAgent both in Windows and Linux. PgAgent seems to ignore pgpass.conf/.pgpass whenever it has 127.0.0.1 (127.0.0.1:5432:*:postgres:postgres) throws an error: *DEBUG: Creating DB connection: user=postgres port=5432 hostaddr=127.0.0.1 dbname=linuxpostgresdb*

Re: Code of Conduct plan

On 06/04/2018 01:46 PM, Tom Lane wrote: "Joshua D. Drake" writes: On 06/03/2018 11:29 AM, Tom Lane wrote: We are now asking for a final round of community comments. Actually, it's intentional that we are not saying that. The idea is that any interaction between PG community members is

Re: Microsoft buys GitHub, is this a threat to open-source

Joshua D. Drake writes: > On 06/04/2018 10:31 AM, Rich Shepard wrote: >> On Mon, 4 Jun 2018, Joshua D. Drake wrote: >> >>> No but it does show why using non open source platforms for open source >>> projects is an inherently bad idea. >> >> Joshua, >> >> Sourceforge seems to be out of favor,

Re: Code of Conduct plan

On 4 June 2018 at 17:53, Tom Lane wrote: > Alvaro Herrera writes: > > On 2018-Jun-05, Gavin Flower wrote: > >> If we are all adults, then we don't need a CoC. > > > "We're all adults" is wishful thinking. Some old people are just kids > > who aged but didn't actually mature. > > I'm sure we'd

Re: Code of Conduct plan

On 2018-06-04 22:26, Alvaro Herrera wrote: On 2018-Jun-05, Gavin Flower wrote: If we are all adults, then we don't need a CoC. "We're all adults" is wishful thinking. Some old people are just kids who aged but didn't actually mature. Also to point out... there is the occasional teen who

Re: Code of Conduct plan

On 2018-Jun-05, Gavin Flower wrote: > If we are all adults, then we don't need a CoC. "We're all adults" is wishful thinking. Some old people are just kids who aged but didn't actually mature. -- Álvaro Herrerahttps://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support,

Re: Code of Conduct plan

On 05/06/18 06:41, Jason Petersen wrote: On Jun 4, 2018, at 10:59 AM, Joshua D. Drake > wrote: "snowflake", I find that term hilarious others find it highly offensive. Which is correct? I don’t think it’s offensive but it plainly fails your “if you wouldn’t

Store login credentials client-side

Hello, I’m looking for a way to store the login credential of my PostgreSQL DB in an external server. With Oracle DB I use Oracle Wallet to reach this goal. Do you know if exists a similar tool for PostgreSQL? Thank you

Re: Microsoft buys GitHub, is this a threat to open-source

2018-06-04 20:34 GMT+02:00 Michael Nolan : > > > On Mon, Jun 4, 2018 at 12:15 PM, Tom Lane wrote: > >> Michael Nolan writes: >> > Microsoft has bought GitHub for $7.5 billion, is this a threat to the >> open >> > source community? >> >> A fair question, but one that seems entirely off-topic for

Re: Code of Conduct plan

> On Jun 4, 2018, at 10:59 AM, Joshua D. Drake wrote: > > "snowflake", I find that term hilarious others find it highly offensive. > Which is correct? I don’t think it’s offensive but it plainly fails your “if you wouldn’t say it to a client, don’t say it here” test. Generally we so-called

Re: Microsoft buys GitHub, is this a threat to open-source

On 4 Jun 2018, at 18:31, Rich Shepard wrote: > On Mon, 4 Jun 2018, Joshua D. Drake wrote: > >> No but it does show why using non open source platforms for open source >> projects is an inherently bad idea. > > Joshua, > > Sourceforge seems to be out of favor, too, so are there any open

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

"David G. Johnston" writes: > On Mon, Jun 4, 2018 at 6:44 AM, pavan95 wrote: >> The main reason for my requirement is to find the time swing between server >> stop and start. > Not all server stops are logged/evented (i.e., crashes), though by > definition all successful starts are (or at least

Re: Code of Conduct plan

On 4 Jun 2018, at 18:24, Justin Clift wrote: > Adding a CoC will change the quantity-of-fules mix _slightly_, depending on > how in-your-face people > are with it. s/quantity-of-fules/quantity-of-rules/ Interesting typo though. :) -- "My grandfather once told me that there are two kinds of

Microsoft buys GitHub, is this a threat to open-source

Microsoft has bought GitHub for $7.5 billion, is this a threat to the open source community? -- Mike Nolan

Re: [MASSMAIL]Re: Code of Conduct plan

El 2018-06-04 12:52, Joshua D. Drake escribió: 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. Please send any public comments to the pgsql-general list (only). If you wish to make a private

Re: Code of Conduct plan

On 06/04/2018 06:33 AM, Benjamin Scherrey wrote:     I did go back and read through the 2016 content rather thoroughly. But where has all the discussion been going on for the last two years? Am I to understand that this effort has been going on in an entirely undocumented manner? I find

Re: Code of Conduct plan

On 06/04/2018 09:44 AM, Ron wrote: If there's been so much Bad Behavior that's so Weakened the Community, then someone's done an excellent job of hiding that Bad Behavior. The inner circle of any community is very good at protecting itself and exerting authority without representation or

Re: Code of Conduct plan

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 that may bring the PostgreSQL project into disrepute, ..." This to me is

Re: Code of Conduct plan

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. Please send any public comments to the pgsql-general list (only). If you wish to make a private comment, you may send it to c...@postgresql.org.

Re: Code of Conduct plan

If there's been so much Bad Behavior that's so Weakened the Community, then someone's done an excellent job of hiding that Bad Behavior. On 06/04/2018 09:57 AM, Evan Macbeth wrote: I just want to chime in and thank all those who worked on this Code of Conduct. It's well thought out, and I'm

Re: Code of Conduct plan

On 06/03/2018 05:57 PM, Jonathan S. Katz wrote: Anyway, a big +1 to the effort of everyone who worked on the CoC for the past several years. From feedback in other forums through the years, I know it does make a difference to have a code of conduct in terms of helping people to feel more

Re: notes from transition to relkind='p'

On Sun, Jun 03, 2018 at 12:13:49PM -0700, Adrian Klaver wrote: > On 06/01/2018 03:14 PM, Justin Pryzby wrote: > >Before I forget any more, this is a brain of issues/considerations/concerns Should have said brain DUMP Keep in mind, I've phrased these as notes, maybe useful to someone else, maybe

Re: Code of Conduct plan

On Sun, 3 Jun 2018 at 22:47, Tom Lane wrote: > In any case, we went over all these sorts of arguments at excruciating > length in 2016. It's quite clear to the core team that a majority of > the community wants a CoC. I don't think any useful purpose will be > served by re-litigating that

Re: Code of Conduct plan

Benjamin Scherrey writes: > I did go back and read through the 2016 content rather thoroughly. But > where has all the discussion been going on for the last two years? It's been private, mostly either (a) the exploration committee responding to comments that were received at PGCon 2016 [1]

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

On Mon, Jun 4, 2018 at 6:44 AM, pavan95 wrote: > The main reason for my requirement is to find the time swing between server > stop and start. > ​Not all server stops are logged/evented (i.e., crashes), though by definition all successful starts are (or at least can be).​ David J.

Re: [HACKERS] Code of Conduct plan

On Mon, Jun 4, 2018 at 7:06 AM, Adrian Klaver wrote: > On 06/03/2018 09:21 PM, David G. Johnston wrote: > >> >> That's pretty much par for the public dynamic of this community. And, as >> noted above, such a policy doesn't need the community at-large's approval: >> it's a document that

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

If i were you, i would parse the logfile as others already mentioned. It is easy and clean. Another option might be to modify the init script and add a timestamp to a file whenever it stops/starts your server. Or maybe you can add to the init file a script that fills in your table, but i m not

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

On 06/04/2018 08:44 AM, pavan95 wrote: Hi Adrian/Melvin, Thanks for your prompt replies. Yeah, I'm aware of that way. But my requirement is to get the server shutdown time whenever that event occurs and insert into a table dynamically!! Is it possible? You want to trap the shutdown action

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

Thank you so much for your replies. On Mon, Jun 4, 2018, 7:25 PM Adrian Klaver wrote: > On 06/04/2018 06:44 AM, pavan95 wrote: > > Hi Adrian/Melvin, > > > > Thanks for your prompt replies. Yeah, I'm aware of that way. > > > > But my requirement is to get the server shutdown time whenever that

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

On 06/04/2018 06:44 AM, pavan95 wrote: Hi Adrian/Melvin, Thanks for your prompt replies. Yeah, I'm aware of that way. But my requirement is to get the server shutdown time whenever that event occurs and insert into a table dynamically!! Is it possible? A quick scan shows no built in function

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

On Mon, Jun 4, 2018 at 9:44 AM, pavan95 wrote: > Hi Adrian/Melvin, > > Thanks for your prompt replies. Yeah, I'm aware of that way. > > But my requirement is to get the server shutdown time whenever that event > occurs and insert into a table dynamically!! Is it possible? > > The main reason for

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

Hi Adrian/Melvin, Thanks for your prompt replies. Yeah, I'm aware of that way. But my requirement is to get the server shutdown time whenever that event occurs and insert into a table dynamically!! Is it possible? The main reason for my requirement is to find the time swing between server stop

Re: Code of Conduct plan

On Mon, Jun 4, 2018 at 4:47 AM, Tom Lane wrote: > Benjamin Scherrey writes: > > Is there some archive of the discussion that brought on this effort and > the > > considerations of the committee itself? I wish I had seen the earlier > > announcements in 2016 as I would have definitely

Re: VBA to connect to postgresql from MS Access

On 06/03/2018 09:30 PM, Łukasz Jarych wrote: Thank you Adrian, in answer to response in link: This connection string is not working for me. How it is not working? Do you get error messages? And my conf file is in attachment. Only this strange DSN less conn string is working: I am not

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

On Mon, Jun 4, 2018 at 9:17 AM, pavan95 wrote: > Hi all, > > Is there any way to get postmaster(postgres database) shutdown time? > Please > help!! > > Thanks in Advance. > > > Regards, > Pavan > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-general- > f1843780.html > > Look

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

On 06/04/2018 06:17 AM, pavan95 wrote: Hi all, Is there any way to get postmaster(postgres database) shutdown time? Please help!! Assuming you have the Postgres logging turned on it will be in the log: The log when the server was shutdown: 2018-06-03 21:11:41.739 PDT-0LOG: database system

How to get postmaster shut down time in postgres?

Hi all, Is there any way to get postmaster(postgres database) shutdown time? Please help!! Thanks in Advance. Regards, Pavan -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

RE: VBA to connect to postgresql from MS Access

From: Łukasz Jarych [mailto:jarys...@gmail.com] Sent: Monday, June 04, 2018 12:30 AM To: Adrian Klaver Cc: pgsql-gene...@postgresql.org >> PG-General Mailing List Subject: Re: VBA to connect to postgresql from MS Access Thank you Adrian, in answer to response in link: This connection