Thread: incorrect resource manager data checksum in record

On Fri, Jun 29, 2018 at 1:14 PM, Devin Christensen <quixoten@gmail.com> wrote:
>> From your description it sounds like it's happening in the middle of
>> streaming, right?
>
> Correct. None of the instances in the chain experience a crash. Most of the
> time I see the "incorrect resource manager data checksum in record" error,
> but I've also seen it manifested as:
>
> invalid magic number 8813 in log segment 000000030000AEC20000009C, offset
> 15335424

I note that that isn't at a segment boundary.  Is that also the case
for the other error?

One theory would be that there is a subtle FS cache coherency problem
between writes and reads of a file from different processes
(causality), on that particular stack.  Maybe not too many programs
pass data through files with IPC to signal progress in this kinda
funky way, but that'd certainly be a violation of POSIX if it didn't
work correctly and I think people would know about that so I feel a
bit silly suggesting it.  To follow that hypothesis to the next step:
I suppose it succeeds after you restart because it requests the whole
segment again and gets a coherent copy all the way down the chain.
Another idea would be that our flush pointer tracking and IPC is
somehow subtly wrong and that's exposed by different timing leading to
incoherent reads, but I feel like we would know about that by now too.

I'm not really a replication expert, so I could be missing something
simple here.  Anyone?

>> I did find this similar complaint that involves an ext4 primary and a
>> btrfs replica:
>
> It is interesting that my issue occurs on the first hop from ZFS to ext4. I
> have not seen any instances of this happening going from the ext4 primary to
> the first ZFS replica.

I happen to have a little office server that uses ZFS so I left it
chugging through a massive pgbench session with a chain of 3 replicas
while I worked on other stuff, and didn't see any problems (no ext4
involved though, this is a FreeBSD box).  I also tried
--wal-segsize=1MB (a feature of 11) to get some more frequent
recycling happening just in case it was relevant.

>> We did have a report recently of ZFS recycling WAL files very slowly
>
> Do you know what version of ZFS that effected? We're currently on 0.6.5.6,
> but could upgrade to 0.7.5 on Ubuntu 18.04

I think that issue is fundamental/all versions, and has something to
with the record size (if you have 128KB ZFS records and someone writes
8KB, it probably needs to read a whole 128KB record in, whereas with
ext4 et al you have 4KB blocks and the OS can very often skip reading
it in because it can see you're entirely overwriting blocks), and
possibly the COW design too (I dunno).  Here's the recent thread,
which points back to an older one, from some Joyent guys who I gather
are heavy ZFS users:

https://www.postgresql.org/message-id/flat/CACPQ5FpEY9CfUF6XKs5sBBuaOoGEiO8KD4SuX06wa4ATsesaqg%40mail.gmail.com

There was a ZoL bug that made headlines recently but that was in 0.7.7
so not relevant to your case.

-- 
Thomas Munro
http://www.enterprisedb.com

Hi,

I'm looking at pgloader to automate data loading into a Postgis enabled Postgres database.

I have seen in the tutorial how the internal point type is supported, and how the postgis extension can be pre-installed by pgloader if necessary, but I can't see how I might take x & y values & save as a postgis point. I guess I could do this via a trigger, but that is hopefully an unnecessary workaround.

if I read data in (say from CSV):

1,tan0104,1,173.567,-43.678

...

to a Postgis table:

create table station

(id         int     primary key,

 trip       char(7)

 station_no int,

 lon_s      decimal(7,4),

 lat_s      decimal(6,4),

 startp     geometry(POINT,4326));

the startp column is populated by the SQL:

startp=ST_SetSRID(ST_MakePoint(lon_s,lat_s),4326)

This creates a point feature from the x (lon) & y (lat) coordinates,

  and specifies the coordinate reference system as lat/lon degrees WGS84 (EPSG:4326) to match the column specification.

How can I implement that in the pgloader command to load the CSV file?

Thanks

Hi Brent,

Yes I think it's possible, simply playing with the TARGET COLUMNS clause of the pgloader command. Would you mind
openingan issue on Github, where I track bug fixes and user requests, so that our conversation is then publicly
archivedand available to other PostGIS and pgloader users?
 

Thanks,
-- 
  Dimitri Fontaine
  dim@tapoueh.org

On Fri, Jun 29, 2018, at 04:33, Brent Wood wrote:
> Hi,
> 
> 
> I'm looking at pgloader to automate data loading into a Postgis enabled 
> Postgres database.
> 
> 
> I have seen in the tutorial how the internal point type is supported, 
> and how the postgis extension can be pre-installed by pgloader if 
> necessary, but I can't see how I might take x & y values & save as a 
> postgis point. I guess I could do this via a trigger, but that is 
> hopefully an unnecessary workaround.
> 
> 
> if I read data in (say from CSV):
> 
> 
> 1,tan0104,1,173.567,-43.678
> 
> ...
> 
> 
> to a Postgis table:
> 
> create table station
> 
> (id         int     primary key,
> 
>  trip       char(7)
> 
>  station_no int,
> 
>  lon_s      decimal(7,4),
> 
>  lat_s      decimal(6,4),
> 
>  startp     geometry(POINT,4326));
> 
> 
> 
> the startp column is populated by the SQL:
> 
> startp=ST_SetSRID(ST_MakePoint(lon_s,lat_s),4326)
> 
> 
> This creates a point feature from the x (lon) & y (lat) coordinates,
> 
>   and specifies the coordinate reference system as lat/lon degrees WGS84 
> (EPSG:4326) to match the column specification.
> 
> 
> How can I implement that in the pgloader command to load the CSV file?
> 
> 
> 
> Thanks
> 
> 
> Brent Wood
> 
> Programme leader: Environmental Information Delivery
> NIWA
> DDI:  +64 (4) 3860529
> 
> 
> 
> Brent Wood
> Principal Technician - GIS and Spatial Data Management
> Programme Leader - Environmental Information Delivery
> +64-4-386-0529 | 301 Evans Bay Parade, Greta Point, Wellington | 
> www.niwa.co.nz<http://www.niwa.co.nz>
> [NIWA]<http://www.niwa.co.nz>
> To ensure compliance with legal requirements and to maintain cyber 
> security standards, NIWA's IT systems are subject to ongoing monitoring, 
> activity logging and auditing. This monitoring and auditing service may 
> be provided by third parties. Such third parties can access information 
> transmitted to, processed by and stored on NIWA's IT systems.
> 
> 
> 
> Email had 1 attachment:
> + image9c19a7.JPG
>   28k (image/jpeg)