| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Giuseppe Broccolo <giuseppe(dot)broccolo(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dump a comment of a TSDictionary |
| Date: | 2017-03-06 22:06:57 |
| Message-ID: | 20170306220657.GB9812@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> Do you want to deal with this whole mess, or shall I have a go at it?
>
> > I'm just about to push the pg_upgrade fixes for large object comments
> > and security labels, followed not too far behind by the fix for the
> > public ACL in pg_dump --clean mode. I have no objection to you handling
> > these and I can go look at some of the other items on my plate.
>
> OK, I'll wait till you've pushed those, just to avoid any risk of merge
> problems.
Alright, I've pushed the large object fix for pg_upgrade, hopefully the
buildfarm will stay clean. I'm going to do a bit more testing on the
public ACL/pg_dump --clean patch, but it's also quite a localized patch,
so I think you're good to go now.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-06 22:14:12 | Re: Re: check failure with -DRELCACHE_FORCE_RELEASE -DCLOBBER_FREED_MEMORY |
| Previous Message | Robert Haas | 2017-03-06 21:58:23 | Re: Performance degradation in TPC-H Q18 |