Re: Postgres calendar?
Hi, On Tue, Oct 04, 2022 at 05:02:28PM -0400, Bruce Momjian wrote: > Would people be interesting in subscribing to a Postgres calendar that > includes dates for minor releases, final minor release dates for major > versions, commit fests, and even Postgres events? For example, it could > include information from: > > https://www.postgresql.org/developer/roadmap/ > https://www.postgresql.org/support/versioning/ > https://commitfest.postgresql.org/ > https://www.postgresql.org/about/events/ > > We could even add information about beta, release candidate, and final > major releases, though the final release dates are usually not public. > > This could be done in Google Calendar, with an exported ICS file, or via > a dedicated ICS file. I could even automate it by scraping our website. Good idea, that could be quite helpful! I'm wondering if the minor versions release dates and EOL info would deserve a dedicated calendar. I know that multiple teams provide their own packages, and they would probably enjoy a curated calendar.
Re: Postgres calendar?
Absolutely, it'd be much easier having this info integrated with my work/personal calendar, as that's how I try and organize things anyways. Thanks for the suggestion. -Adam On Tue, Oct 4, 2022 at 5:02 PM Bruce Momjian wrote: > Would people be interesting in subscribing to a Postgres calendar that > includes dates for minor releases, final minor release dates for major > versions, commit fests, and even Postgres events? For example, it could > include information from: > > https://www.postgresql.org/developer/roadmap/ > https://www.postgresql.org/support/versioning/ > https://commitfest.postgresql.org/ > https://www.postgresql.org/about/events/ > > We could even add information about beta, release candidate, and final > major releases, though the final release dates are usually not public. > > This could be done in Google Calendar, with an exported ICS file, or via > a dedicated ICS file. I could even automate it by scraping our website. > > -- > Bruce Momjian https://momjian.us > EDB https://enterprisedb.com > > Indecision is a decision. Inaction is an action. Mark Batterson > > > >
Re: Postgres calendar?
Bruce, It would certainly help in keeping track of things. JD On Tue, Oct 4, 2022 at 2:02 PM Bruce Momjian wrote: > Would people be interesting in subscribing to a Postgres calendar that > includes dates for minor releases, final minor release dates for major > versions, commit fests, and even Postgres events? For example, it could > include information from: > > https://www.postgresql.org/developer/roadmap/ > https://www.postgresql.org/support/versioning/ > https://commitfest.postgresql.org/ > https://www.postgresql.org/about/events/ > > We could even add information about beta, release candidate, and final > major releases, though the final release dates are usually not public. > > This could be done in Google Calendar, with an exported ICS file, or via > a dedicated ICS file. I could even automate it by scraping our website. > > -- > Bruce Momjian https://momjian.us > EDB https://enterprisedb.com > > Indecision is a decision. Inaction is an action. Mark Batterson > > > >
Re: fully qualified domain names and .pgpass
On 10/4/22 12:33, Alvaro Herrera wrote: On 2022-Oct-04, Ron wrote: Sometimes (both interactively and via script) I access a remote Pg server via just the bare host name "foobar", and other times via the FQDN "foobar.example.com". I've only been able to get this to work by having two lines in the .pgpass file: Maybe it would be simpler to do this using a service definition in the ~/.pg_service.conf file. https://www.postgresql.org/docs/current/libpq-pgservice.html That did solve my problem: pg_backrest --dbname=service=basebackup -- Angular momentum makes the world go 'round.
Re: Postgres calendar?
Em ter., 4 de out. de 2022 às 18:02, Bruce Momjian escreveu: > > Would people be interesting in subscribing to a Postgres calendar that > includes dates for minor releases, final minor release dates for major > versions, commit fests, and even Postgres events? For example, it could > include information from: > > https://www.postgresql.org/developer/roadmap/ > https://www.postgresql.org/support/versioning/ > https://commitfest.postgresql.org/ > https://www.postgresql.org/about/events/ > > We could even add information about beta, release candidate, and final > major releases, though the final release dates are usually not public. > > This could be done in Google Calendar, with an exported ICS file, or via > a dedicated ICS file. I could even automate it by scraping our website. > +1 This information is very useful. Regards, -- Fabrízio Mello
Postgres calendar?
Would people be interesting in subscribing to a Postgres calendar that includes dates for minor releases, final minor release dates for major versions, commit fests, and even Postgres events? For example, it could include information from: https://www.postgresql.org/developer/roadmap/ https://www.postgresql.org/support/versioning/ https://commitfest.postgresql.org/ https://www.postgresql.org/about/events/ We could even add information about beta, release candidate, and final major releases, though the final release dates are usually not public. This could be done in Google Calendar, with an exported ICS file, or via a dedicated ICS file. I could even automate it by scraping our website. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson
Re: fully qualified domain names and .pgpass
On Tue, Oct 4, 2022 at 1:02 PM Ron wrote: > > Sometimes (both interactively and via script) I access a remote Pg server > via just the bare host name "foobar", and other times via the FQDN > "foobar.example.com". > > I've only been able to get this to work by having two lines in the .pgpass > file: > > foobar:5432:postgres:Allegedly.Strong.Password > foobar.example.com:5432:postgres:Allegedly.Strong.Password > > But I'd rather have only one line. Is there any way to do that? This is not a FQDN: > "foobar.example.com". A FQDN ends in dot '.' The dot denotes the top of the dns tree. So a FQDN for the host would be: foobar.example.com. Anyone who tells you any different has not read W. Richard Stevens :) Jeff
Re: fully qualified domain names and .pgpass
On 10/4/22 10:02 AM, Ron wrote: Sometimes (both interactively and via script) I access a remote Pg server via just the bare host name "foobar", and other times via the FQDN "foobar.example.com". I've only been able to get this to work by having two lines in the .pgpass file: foobar:5432:postgres:Allegedly.Strong.Password foobar.example.com:5432:postgres:Allegedly.Strong.Password But I'd rather have only one line. Is there any way to do that? Would a service file: https://www.postgresql.org/docs/14/libpq-pgservice.html work? -- Adrian Klaver adrian.kla...@aklaver.com
Re: fully qualified domain names and .pgpass
On 2022-Oct-04, Ron wrote: > Sometimes (both interactively and via script) I access a remote Pg server > via just the bare host name "foobar", and other times via the FQDN > "foobar.example.com". > > I've only been able to get this to work by having two lines in the .pgpass > file: Maybe it would be simpler to do this using a service definition in the ~/.pg_service.conf file. https://www.postgresql.org/docs/current/libpq-pgservice.html -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
fully qualified domain names and .pgpass
Sometimes (both interactively and via script) I access a remote Pg server via just the bare host name "foobar", and other times via the FQDN "foobar.example.com". I've only been able to get this to work by having two lines in the .pgpass file: foobar:5432:postgres:Allegedly.Strong.Password foobar.example.com:5432:postgres:Allegedly.Strong.Password But I'd rather have only one line. Is there any way to do that? -- Angular momentum makes the world go 'round.
PGSQL Phriday #001 - Two truths and a lie about PostgreSQL
Hello everyone! Many months ago at PGConf NYC 2021 and on the pgsql-advocacy email list, I talked about starting a monthly blogging event for the PostgreSQL community. Two weeks ago I wrote a blog post explaining how the monthly event would work and some of the first community members to host the first six+ months. (https://www.softwareandbooz.com/introducing-psql-phriday/) I'm pleased to share here that the first invite has been posted on my blog and I'd be thrilled to have anyone contribute a blog post to the initiative this Friday, October 7. The "rules" for contributing a post are outlined in the invite, but please feel free to reach out to me if you have any questions. https://www.softwareandbooz.com/pgsql-phriday-001-invite/ Regards, Ryan Booz
