Re: [HACKERS] SQL MERGE patches for PostgreSQL Versions

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] SQL MERGE patches for PostgreSQL Versions
Дата
Msg-id CAB7nPqSaXbysSF4sfmU8PzoDbtrRuYKwdGCD97ogD533B=e1fg@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] SQL MERGE patches for PostgreSQL Versions  (Kang Yuzhe <tiggreen87@gmail.com>)
Ответы Re: [HACKERS] SQL MERGE patches for PostgreSQL Versions  (Kang Yuzhe <tiggreen87@gmail.com>)
Список pgsql-hackers
On Thu, Jun 22, 2017 at 5:05 PM, Kang Yuzhe <tiggreen87@gmail.com> wrote:
> First my apology if I appear to be a jerk or not following the policy.

No problem.

> I emailed Boxuan Zhai who was  in charge of the SQL Merge keyword in
> 2010 of GSoC but without reply.
>
> I want to apply merge_v201.patch to specific PG version.
>
> It failed saying 1 or 2 of 5 hunk failed.
>
> My question is:
>  1. Given x old patch of PG, is it possible to know  to which PG
> version can be applied?
>  2. If not possible, can someone tell me the general approach to apply
> given old patch(merge_v201.patch) to PG.
>  3. Who was the mentor of SQL Merge of GSoC in 2010 and if present in
> this PG Community, can he/she tell me which PG version was applied SQL
> Merge?
>
> My goal is to apply SQL Merge patch into PG successfully and to from
> learn the code applied.

If the goal is to learn from the past code and you are not really
willing to fix code conflicts, you could always try to apply a patch
of 2010 using a version of the master branch located between 8.4 and
9.0 :)
-- 
Michael



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: [HACKERS] pg_stop_backup(wait_for_archive := true) on standby server
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: [HACKERS] Autovacuum launcher occurs error when cancelled by SIGINT