Re: A problem about partitionwise join

Поиск
Список
Период
Сортировка
Искать
От
Jacob Champion
Тема
Re: A problem about partitionwise join
Дата
Msg-id
fbb8e102-ff92-9d9f-6360-23fd7b274899@timescale.com
Ответ на
Список
Дерево обсуждения
A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Amit Langote <amitlangote09@gmail.com>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Etsuro Fujita <etsuro.fujita@gmail.com>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Dilip Kumar <dilipbalaut@gmail.com>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Dilip Kumar <dilipbalaut@gmail.com>
Re: A problem about partitionwise join Etsuro Fujita <etsuro.fujita@gmail.com>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Etsuro Fujita <etsuro.fujita@gmail.com>
Re: A problem about partitionwise join Etsuro Fujita <etsuro.fujita@gmail.com>
Re: A problem about partitionwise join Michael Paquier <michael@paquier.xyz>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Etsuro Fujita <etsuro.fujita@gmail.com>
Re: A problem about partitionwise join Richard Guo <riguo@pivotal.io>
Re: A problem about partitionwise join Tom Lane <tgl@sss.pgh.pa.us>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Tom Lane <tgl@sss.pgh.pa.us>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Jaime Casanova <jcasanov@systemguards.com.ec>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Jacob Champion <jchampion@timescale.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Robert Haas <robertmhaas@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Robert Haas <robertmhaas@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: A problem about partitionwise join Richard Guo <guofenglinux@gmail.com>
Re: A problem about partitionwise join Tom Lane <tgl@sss.pgh.pa.us>
Re: A problem about partitionwise join Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
As discussed in [1], we're taking this opportunity to return some
patchsets that don't appear to be getting enough reviewer interest.

This is not a rejection, since we don't necessarily think there's
anything unacceptable about the entry, but it differs from a standard
"Returned with Feedback" in that there's probably not much actionable
feedback at all. Rather than code changes, what this patch needs is more
community interest. You might

- ask people for help with your approach,
- see if there are similar patches that your code could supplement,
- get interested parties to agree to review your patch in a CF, or
- possibly present the functionality in a way that's easier to review
  overall.

(Doing these things is no guarantee that there will be interest, but
it's hopefully better than endlessly rebasing a patchset that is not
receiving any feedback from the community.)

Once you think you've built up some community support and the patchset
is ready for review, you (or any interested party) can resurrect the
patch entry by visiting

    https://commitfest.postgresql.org/38/2266/

and changing the status to "Needs Review", and then changing the
status again to "Move to next CF". (Don't forget the second step;
hopefully we will have streamlined this in the near future!)

Thanks,
--Jacob

[1]
https://postgr.es/m/flat/0ab66589-2f71-69b3-2002-49e821740b0d%40timescale.com


В списке pgsql-hackers по дате отправления
От: Jacob Champion
Дата:
От: Tom Lane
Дата:
FAQ