| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-03 00:02:31 |
| Message-ID: | CAMjNa7fQfKirZOZjzbht1za7mAvj3DLzpGpxgWqVaH3UxMWotw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> > 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
That makes sense now, I was reading that section as if it were talking
about bytea, not LO.
Thanks for pointing that out!
- Adam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2020-07-03 06:46:34 | Re: survey: psql syntax errors abort my transactions |
| Previous Message | Adrian Klaver | 2020-07-02 23:32:19 | Re: Does TOAST really compress the complete row? |