[Tile-serving] osm2pgsql DB keeps corrupting on power loss

[Stephen - junkmail]

That makes a lot of sense. Maybe I'll submit a PR for dropping the 
unnecessary tables before generate indexes when using the --drop 
parameter. Seems like it would save quite a lot of space.

On 2019-08-04 8:19 p.m., Kevin Kenny wrote:
> On Sun, Aug 4, 2019 at 6:30 PM Stephen - junkmail <junkmail at scd31.com> wrote:
>> If I understand that right, it means planet_osm_polygon and planet_osm_line are unlogged. That makes sense as they're the ones being corrupted. I am absolutely positive I didn't use the --unlogged option, especially when I reimported after I received your email. Is there anything else that would cause the tables to be unlogged?
> If I recall correctly, the tables are unlogged during the import for
> speed. That's ordinarily not a risk, since osm2pgsql doesn't provide
> any method to restart an import in progress.
>
> But what you're doing is to build the indices manually, without
> turning logging on at the end, after osm2pgsql has aborted. That's
> certain to leave logging turned off, since neither you nor osm2pgsql
> has turned it on.