From: | Fernando Hevia <fhevia(at)gmail(dot)com> |
---|---|
To: | sacrophyte(at)gmail(dot)com |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Training for seasoned DBAs new to postgres? |
Date: | 2023-07-14 03:50:24 |
Message-ID: | CAGYT1XTTFabmOethb=K3U5SiayMAxUPG1NeTeq4k+kpLwq3ukg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
El jue, 13 jul 2023 a la(s) 09:34, Charles Schultz (sacrophyte(at)gmail(dot)com)
escribió:
> A couple folks have already responded privately with some ideas. I have
> another related question - for Oracle and MS SQL Server we pay for support.
> As Postgres is open-source, what is the popular opinion from this group on
> getting immediate, 24x7 support for postgres issues?
>
Hi Charles.
Postgres being open-source means you don't need to pay to use it but the
art of using it well is no different than other databases.
You pay for Oracle and MS SQL support to have experts available in case of
need. With Postgres it is the same. Those experts do exist and many of them
happen to work for companies that provide excellent support services.
Of course you can go by without paid support and rely on the Internet and
the online community of experts to provide free advice if in need. Postgres
is very stable and can run for years on surprisingly well with minimal or
no maintenance at all.
But... if you run mission critical databases on Postgres and your team
lacks solid Postgres DBA skills, I would say that paying for support is the
sound thing to do.
Regards,
Fernando
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hoover | 2023-07-17 00:30:59 | Help with logical replication: pg_replication_slots.active_pid is null???? |
Previous Message | Johannes Truschnigg | 2023-07-13 14:12:32 | Re: Training for seasoned DBAs new to postgres? |