libpq work

From: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
To: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: libpq work
Date: 2000-07-10 05:45:47
Message-ID: 3969630B.806AB0C6@nimrod.itg.telecom.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Well after hacking around on libpq for a few days I'm starting to
understand some of the subtley of what's going on. I'm also
understanding that it's complex enough that I'm not going to be sure
anymore about what subtleties I might break. It's a pity there isn't
regression tests for this so I know for sure what is expected to happen,
and what subtle features are in there.

Anyway for this reason, I think I'm going to go back and simply add the
features I want to libpq. I've learnt enough that I think I know now how
to do it, with a minimum of patches.

Longer term, I'd like to implement SQL3 on top of libpq, then get some
comprehensive test harnesses in place, and then slowly dissolve libpq.
But without those regression tests, it's a bit scary. I assume that the
psql tests wouldn't fully exercise libpq what with the asynchonous stuff
etc?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-07-10 05:57:09 postmaster errors with index on temp table?
Previous Message Tom Lane 2000-07-10 05:14:37 Re: more corruption