Re: The plan for FDW-based sharding

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: The plan for FDW-based sharding
Дата
Msg-id CAA-aLv7K9HPMcw9PESGA8TyqymOT9yyH_82StvcBb6c45_CjHg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: The plan for FDW-based sharding  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-hackers
<p dir="ltr">On 6 Mar 2016 8:27 p.m., "Peter Geoghegan" <<a href="mailto:pg@heroku.com">pg@heroku.com</a>>
wrote:<br/> ><br /> > On Fri, Mar 4, 2016 at 4:41 PM, Robert Haas <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br /> > > Yeah, I agree with that.  I am
utterlymystified by why Bruce keeps<br /> > > beating this drum, and am frankly pretty annoyed about it.  In
the<br/> > > first place, he seems to think that he invented the idea of using FDWs<br /> > > for sharding
inPostgreSQL, but I don't think that's true.  I think it<br /> > > was partly my idea, and partly something that
theNTT folks have been<br /> > > working on for years (cf, e.g.,<br /> > >
cb1ca4d800621dcae67ca6c799006de99fa4f0a5). As far as I understand it,<br /> > > Bruce came in near the end of
thatconversation and now wants to claim<br /> > > credit for something that doesn't really exist yet and, to the
extent<br/> > > that it does exist, wasn't even his idea.<br /> ><br /> > I think that it's easy to have
thesame idea as someone else<br /> > independently. I've had that happen several times myself; ideas that<br /> >
otherpeople had that I felt I could have easily had myself, or did in<br /> > fact have. Most of the ideas that I
haveare fairly heavily based on<br /> > known techniques. I don't think that I've ever creating a PostgreSQL<br />
>feature that was in some way truly original, except perhaps for some<br /> > aspects of how UPSERT works.<p
dir="ltr">Everythingis a remix.<p dir="ltr">Thom 

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

Предыдущее
От: Joe Conway
Дата:
Сообщение: Re: Badly designed error reporting code in controldata_utils.c
Следующее
От: Tom Lane
Дата:
Сообщение: Re: character_not_in_repertoire vs. untranslatable_character