On Sat, Feb 02, 2013 at 10:12:54AM -0500, Bruce Momjian wrote:
> On Sat, Feb 2, 2013 at 09:51:13AM -0500, Noah Misch wrote:
> > Let's touch on the exception in passing by using the phrase "last truncated",
> > giving this wording for both the second and the third COPY FREEZE error sites:
> >
> > cannot perform FREEZE because the table was not created or last
> > truncated in the current subtransaction
>
> Well, so you are saying that there really isn't any use-visible logic
> for those messages to be different, i.e. that the transaction id can be
> set to invalid even if we created/truncated in the same transaction, but
> not the same subtransaction?
Right. The latest committed code makes sense to me.
