On 6/11/19 11:15 AM, Karsten Hilbert wrote:
The problem I hope to protect against with this approach: the
CREATE DATABASE might untaint corrupted data from a bad disk
block into a good disk block virtue of doing a file level
copy.
I hope my reasoning isn't going astray.
As I understand it chec
> > The problem I hope to protect against with this approach: the
> > CREATE DATABASE might untaint corrupted data from a bad disk
> > block into a good disk block virtue of doing a file level
> > copy.
> >
> > I hope my reasoning isn't going astray.
>
> As I understand it checksums are done on the
On 6/11/19 12:15 AM, Karsten Hilbert wrote:
Dear Adrian,
Sure, but that much depends on what (or rather, where) the
"new cluster" actually is.
In my case I want to make sure that - before a run of "CREATE
DATABASE new TEMPLATE old" - I can be reasonable sure that
the disk blocks underlying "o
Dear Tom,
On Fri, Jun 07, 2019 at 11:41:36AM -0400, Tom Lane wrote:
> On 6/6/19 6:50 AM, Karsten Hilbert wrote:
> >> The current canonical solution (?) for verifying checksums in
> >> an existing database is, to may understanding, to pg_dump it
> >> (to /dev/null, perhaps):
> >> as that will read
Dear Adrian,
On Fri, Jun 07, 2019 at 08:02:32AM -0700, Adrian Klaver wrote:
> On 6/6/19 6:50 AM, Karsten Hilbert wrote:
> > The current canonical solution (?) for verifying checksums in
> > an existing database is, to may understanding, to pg_dump it
> > (to /dev/null, perhaps):
> >
> > pg_du
On 6/6/19 6:50 AM, Karsten Hilbert wrote:
>> The current canonical solution (?) for verifying checksums in
>> an existing database is, to may understanding, to pg_dump it
>> (to /dev/null, perhaps):
>> as that will read and verify all blocks related to the dump
>> of that database.
FWIW, that does
On 6/6/19 6:50 AM, Karsten Hilbert wrote:
Now that it is established that CREATE DATABASE does not
verify checksums on the template I have a followup question.
The current canonical solution (?) for verifying checksums in
an existing database is, to may understanding, to pg_dump it
(to /dev/null
Now that it is established that CREATE DATABASE does not
verify checksums on the template I have a followup question.
The current canonical solution (?) for verifying checksums in
an existing database is, to may understanding, to pg_dump it
(to /dev/null, perhaps):
pg_dump --username=...
