From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | David Steele <david(at)pgmasters(dot)net>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Checksum errors in pg_stat_database |
Date: | 2019-03-04 19:31:09 |
Message-ID: | CAOBaU_ZAmGznYPwjkcVPR32M7aL5BsspeCHo__Q5UOYnWLkj7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 22, 2019 at 3:01 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> It tracks things that happen in the general backends. Possibly we should also consider counting the errors actually found when running base backups? OTOH, that part of the code doesn't really track things like databases (as it operates just on the raw data directory underneath), so that implementation would definitely not be as clean...
Sorry I just realized that I totally forgot this part of the thread.
While it's true that we operate on raw directory, I see that sendDir()
already setup a isDbDir var, and if this is true lastDir should
contain the oid of the underlying database. Wouldn't it be enough to
call sendFile() using this, something like (untested):
if (!sizeonly)
- sent = sendFile(pathbuf, pathbuf + basepathlen + 1, &statbuf, true);
+ sent = sendFile(pathbuf, pathbuf + basepathlen + 1, &statbuf, true,
isDbDir ? pg_atoi(lastDir+1, 4) : InvalidOid);
and accordingly report any checksum error from sendFile()?
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-03-04 19:41:00 | Re: psql display of foreign keys |
Previous Message | Paul Ramsey | 2019-03-04 19:20:45 | Re: Allowing extensions to supply operator-/function-specific info |