From: | Michael Robinson <robinson(at)netrinsics(dot)com> |
---|---|
To: | pgsql-hackers(at)hub(dot)org |
Subject: | xid type |
Date: | 1999-11-05 04:01:25 |
Message-ID: | 199911050401.MAA00803@netrinsics.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Is there a fundamental rationale underlying this behavior, or is this
merely something no one has bothered to do:
=> select min(xmin) from mytable where xmax = 0;
ERROR: Unable to select an aggregate function min(xid)
=> select max(xmin) from mytable;
ERROR: Unable to select an aggregate function max(xid)
=> select * from mytable where xmin > 150000;
ERROR: Unable to identify an operator '>' for types 'xid' and 'int4'
You will have to retype this query using an explicit cast
=> select * from mytable where xmin > 150000::xid;
ERROR: Unable to identify an operator '>' for types 'xid' and 'xid'
You will have to retype this query using an explicit cast
=> select * from mytable where xmin::int4 > 150000;
ERROR: No such function 'int4' with the specified attributes
The reason I ask is that it would be fairly straightforward to implement
a poor-man's database replication server if this worked.
-Michael Robinson
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-11-05 05:41:14 | Re: [HACKERS] ERROR: infinite recursion in proc_exit |
Previous Message | Kristofer Munn | 1999-11-05 03:44:55 | ERROR: infinite recursion in proc_exit |