Bonjour Michaël,
It would like to keep "data checksums" in the output,
You can do as you feel.
I have decided that PostgreSQL is a mouthful, thus I'm rather using
"Postgres".
Changing that in one tool and not everything would of course be really
silly. And if you want to bring up the ren
On Fri, Aug 23, 2019 at 09:59:25AM +0200, Magnus Hagander wrote:
> I think trigger is a bad word to use there, but I was already thinking to
> suggest something like "pg_checksums manages or verifies checksums in a
> PostgreSQL cluster", if that doesn't end up being too long?
Doesn't "manage" some
On Fri, Aug 23, 2019 at 8:49 AM Fabien COELHO wrote:
>
> Hello Peter,
>
> > With the additional functionality, the --help synopsis of pg_checksums
> > has gotten quite long:
> >
> > pg_checksums enables, disables, or verifies data checksums in a
> > PostgreSQL database cluster.
> >
> > Can we
Hello Peter,
With the additional functionality, the --help synopsis of pg_checksums
has gotten quite long:
pg_checksums enables, disables, or verifies data checksums in a
PostgreSQL database cluster.
Can we try to shorten this a bit? Maybe
pg_checksums manages data checksums in a Post
With the additional functionality, the --help synopsis of pg_checksums
has gotten quite long:
pg_checksums enables, disables, or verifies data checksums in a
PostgreSQL database cluster.
Can we try to shorten this a bit? Maybe
pg_checksums manages data checksums in a PostgreSQL databas
