Re: Postgres Architecture

2023-10-18 Thread Bruce Momjian
On Tue, Oct 17, 2023 at 08:39:49AM +1100, Timothy Nelson wrote: > Great!  I'm not surprised it's been around a long time -- I didn't think I > could be the only one to think of it.   > > Thanks for the heads-up on Postgres-XL -- I'd missed that one somehow.  > > I'm going to include the words "ar

Re: Postgres Architecture

2023-10-16 Thread Tom Lane
Timothy Nelson writes: > Great! I'm not surprised it's been around a long time -- I didn't think I > could be the only one to think of it. > Thanks for the heads-up on Postgres-XL -- I'd missed that one somehow. FWIW, we also have some in-core history with passing plans around, for parallel-quer

Re: Postgres Architecture

2023-10-16 Thread Timothy Nelson
Great! I'm not surprised it's been around a long time -- I didn't think I could be the only one to think of it. Thanks for the heads-up on Postgres-XL -- I'd missed that one somehow. I'm going to include the words "architecture" and "replication" so that people searching the archives in the futu

Re: Postgres Architecture

2023-10-16 Thread Jonah H. Harris
On Mon, Oct 16, 2023 at 6:42 AM Timothy Nelson wrote: > I'm expecting that people will pick the idea apart, and wanted to know > what people think of it. > Thanks for the proposal. This is actually a model that's been around for a very long time. And, in fact, variations of it (e.g. parsing done