| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | digoal(at)126(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14155: bloom index error with unlogged table |
| Date: | 2016-05-25 01:11:05 |
| Message-ID: | 27605.1464138665@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> Yeah, it looks like nobody ever tested bloom's unlogged-index support;
>> it doesn't work or even come very close to working. Will fix, thanks
>> for the report!
> To be honest, I began hacking around that to address the issue, though
> I don't have yet something to post... So I guess that there is nothing
> I need to do? Or do you need a patch?
Nah, I just pushed something ... but if you'd like to go over the
documentation thread David was complaining about and produce a cleaned-up
docs patch, that would be pretty helpful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-05-25 01:13:12 | Re: BUG #14155: bloom index error with unlogged table |
| Previous Message | Michael Paquier | 2016-05-25 01:04:53 | Re: BUG #14155: bloom index error with unlogged table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-05-25 01:13:12 | Re: BUG #14155: bloom index error with unlogged table |
| Previous Message | Robert Haas | 2016-05-25 01:09:52 | Re: Parallel safety tagging of extension functions |