From: | Ken Johanson <pg-user(at)kensystem(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | V4 protocol, extensible? |
Date: | 2007-01-04 23:08:52 |
Message-ID: | 459D8904.5040107@kensystem.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In another thread I was made aware that current protocol may not be
easily extensible (if at all), and so the backend-data a certain driver
needs may not be so easily added.
http://www.postgresql.org/docs/current/static/protocol-message-formats.html
So if there is not already a roadmap for this, one idea may be to use
some kind of key-length-value type encoding, which seems to be one of
the most accepted formats for extensible streams (though I am by no
means an expert). Names could just be ints/oids and not chars to their
real name.
Just wanted to see if anyone had any thoughts on this, or if my
presumption that metatdata in the current V3 cannot be easily added too,
is wrong.
Thank you,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2007-01-04 23:34:03 | Re: ideas for auto-processing patches |
Previous Message | Dave Page | 2007-01-04 22:55:52 | Re: Problem with windows installer |