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
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 t
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
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 t
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 info
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/
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
> fil
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:p
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 wou
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
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
11 matches
Mail list logo
