| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Kellerer <shammat(at)gmx(dot)net>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Does TOAST really compress the complete row? |
| Date: | 2020-07-02 23:32:19 |
| Message-ID: | f1817d2a-0300-bf7e-2b55-1883a8a1fd26@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 7/2/20 4:29 PM, Adam Brusselback wrote:
> Another thing that was said I wasn't aware of and have not been able to
> find any evidence to support:
https://www.postgresql.org/docs/12/logical-replication-restrictions.html
"Large objects (see Chapter 34) are not replicated. There is no
workaround for that, other than storing data in normal tables."
Of course that does not apply to bytea:
https://www.postgresql.org/docs/12/datatype-binary.html
>
> > 10. Blobs don’t participate in Logical replication.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brusselback | 2020-07-03 00:02:31 | Re: Does TOAST really compress the complete row? |
| Previous Message | Adam Brusselback | 2020-07-02 23:29:02 | Re: Does TOAST really compress the complete row? |