| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Attempt to consolidate reading of XLOG page |
| Date: | 2019-05-21 09:11:37 |
| Message-ID: | 15959.1558429897@spoje.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It seems to me that it's better to unwind the stack i.e. have the
> function return the error information to the caller and let the caller
> do as it likes.
Thanks for a hint. The next version tries to do that.
--
Antonin Houska
Web: https://www.cybertec-postgresql.com
| Attachment | Content-Type | Size |
|---|---|---|
| v03_001_Unexport_XLogReaderInvalReadState.patch | text/x-diff | 1.7 KB |
| v03_002_Remove_TLI_argument_from_XLR_callback.patch | text/x-diff | 9.8 KB |
| v03_003_Introduce_XLogSegment.patch | text/x-diff | 17.9 KB |
| v03_004_Use_only_one_implementation_of_XLogRead.patch | text/x-diff | 15.0 KB |
| v03_005_Cleanup.patch | text/x-diff | 13.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2019-05-21 12:01:47 | A few more opportunities to use TupleTableSlotOps fields |
| Previous Message | Michael Paquier | 2019-05-21 08:24:57 | Re: with oids option not removed in pg_dumpall |