Re: Statistics Import and Export - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Statistics Import and Export
Date
Msg-id CADkLM=c0dOJZUQuWzVcE2BsJSVRGcX7HkJH8wYjo+OD83WFqcg@mail.gmail.com
Whole thread Raw
In response to Re: Statistics Import and Export  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Statistics Import and Export
List pgsql-hackers
* Changed to use LookupExplicitNamespace()

Seems good.
 
* Added test for temp tables

+1
 
* Doc fixes

So this patch swings the pendulum a bit back towards accepting some things as errors. That's understandable, as we're never going to have a situation where we can guarantee that the restore functions never generate an error, so the best we can do is to draw the error-versus-warning line at a place that:

* doesn't mess up flawed restores that we would otherwise expect to complete at least partially
* is easy for us to understand
* is easy for us to explain
* we can live with for the next couple of decades

I don't know where that line should be drawn, so if people are happy with Jeff's demarcation, then less roll with it.
 

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
Next
From: Nathan Bossart
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset