| From: | Taylor Vesely <tvesely(at)pivotal(dot)io> |
|---|---|
| To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Alexandra Wang <lewang(at)pivotal(dot)io>, Ashwin Agrawal <aagrawal(at)pivotal(dot)io>, DEV_OPS <devops(at)ww-it(dot)cn>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Zedstore - compressed in-core columnar storage |
| Date: | 2019-10-28 22:22:10 |
| Message-ID: | CAFaX_4LbenqERsEMbxfTYXzpmvysL_p=o2G-tgDZs_=6eiryCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> When a zedstore table is queried using *invalid* ctid, the server
> crashes due to assertion failure. See below,
>
> postgres=# select * from t2 where ctid = '(0, 0)';
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
Thank you for pointing that out! I will look into fixing that some
time this week. If we run without assertions the query still fails
with this error because zedstoream_tuple_tid_valid incorrectly reports
the TID as valid:
ERROR: arrived at incorrect block 2 while descending zedstore btree
> I believe above should have either returned 1 rows or failed with some
> user friendly error.
Agreed. I think it should match the behavior of heap as closely as
possible.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-10-28 22:32:18 | Re: WIP: expression evaluation improvements |
| Previous Message | Tom Lane | 2019-10-28 22:00:21 | Re: vacuum on table1 skips rows because of a query on table2 |