| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: walprotocol.h vs frontends |
| Date: | 2011-08-15 21:50:15 |
| Message-ID: | m24o1itkdk.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Why not have a specific protocol message to indicate a change of filename?
>> I don't mean a WAL message, I mean a streaming protocol message.
>
> That we could have, and it would work as long as it's always sent as
> the first packet in any stream.
>
> If we do that, we should probably make it a general metadata package -
> including things like segment size as well...
I think this could be made an opt-in: the streaming client would have to
ask for it when connecting to the walsender (or maybe whenever in the
connection stream, I don't know).
Then it can even be backported, and it won't add anything to core
clients streaming data.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2011-08-15 21:53:19 | Re: index-only scans |
| Previous Message | Greg Stark | 2011-08-15 21:49:47 | Re: Should we have an optional limit on the recursion depth of recursive CTEs? |