I would like to do a interface change in pgcrypto. (Good
timing, I know :)) At the moment the digest() function returns
hexadecimal coded hash, but I want it to return pure binary. I
have also included functions encode() and decode() which support
'base64' and 'hex' encodings, so if anyone ne
On Sat, Jan 20, 2001 at 01:31:49PM -0500, Tom Lane wrote:
> Given the infrequency of use of postfix operators compared to prefix,
> I am inclined to think that we should change the grammar to make the
> latter easier to use at the expense of the former. On the other hand,
> it seems there's a pre
Finally found a log analyzer that could parse/handle the logs for
http://www.postgresql.org ... the following is the results. It doesn't
include the mirrors, which I'd be curious as to how much they get on top
of this, but 1,548,354 Requests in last 7 days ...
http://www.postgresql.org/
Denis Perchine <[EMAIL PROTECTED]> writes:
>> lo_import and lo_export always execute in a transaction, just like any
>> other backend operation. There is no need to force them to be done in
>> a transaction block. If you're not clear about this, perhaps you need
>> to review the difference betwe
On Sat, Jan 20, 2001 at 05:35:41PM -0500, Tom Lane wrote:
> Frank Joerdens <[EMAIL PROTECTED]> writes:
> > I haven't tried everything to recover from this yet, but will quickly
> > try to document the crash before I lose track of what exactly went
> > into it and what I did: Basically I deleted a
> Main open item is the handling of hex strings: they are still converted
> to integers by default. They could be BLOBs or bit strings, and the SQL
> standard gives no hint, so it is not clear what the solution should be.
Should I add this to the TODO list?
>
> The only other complaint has been
