On Fri, May 12, 2017 at 1:12 PM, Andres Freund <and...@anarazel.de> wrote: > Given that a lot of data types have a architecture dependent representation, > it seems somewhat unrealistic and expensive to have a hard rule to keep them > architecture agnostic. And if that's not guaranteed, then I'm doubtful it > makes sense as a soft rule either.
That's a good point, but the flip side is that, if we don't have such a rule, a pg_dump of a hash-partitioned table on one architecture might fail to restore on another architecture. Today, I believe that, while the actual database cluster is architecture-dependent, a pg_dump is architecture-independent. Is it OK to lose that property? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers