You are both right.
Your explanation, Steve, was the light that got me going on a simpler
solution along the lines of what Tom suggested. I didn't really need
AGE, and upon digging in, couldn't even remember why I had chosen that
in the first place.
Postgres is the bomb!
Thanks guys.
Steve Crawfor
Hello all,
Many thanks for this fine product.
We began encountering some unexpected date related errors this week and
after further investigation found the following. We use the postgres AGE
function in a custom function. The AGE function has begun to throw some
unanticipated results back. This has
I have experienced this in the past with members of groups, but now with
relation ACLs. It goes like this:
Certain users are given specific permissions of different tables and
such.
The users are later dropped but reference to them remains in the ACL as
their former ID number.
When trying to revoke
DHS Club
Jeff wrote:
>
> On Wed, 29 Oct 2003 11:53:38 -0500
> DHS Webmaster <[EMAIL PROTECTED]> wrote:
>
> > We vacuum our working database nightly. Although this is not a 'full',
> > we don't exclude any tables. We don't do anything with template1
This thread caught my eye and I decided to look at our pg_clog
directory. Sure enough we have got every clog file since we upgraded
back in April, - 02F8.
We vacuum our working database nightly. Although this is not a 'full',
we don't exclude any tables. We don't do anything with template1
(kn
What we do since 2 queries are necessary anyway, is to select the
NEXTVAL which gives us our 'record id' up front. Then when we do our
insert, we include that field with the value we just selected from our
sequence and we're all set. Of course if the insert fails for some
reason, then you will have
Hello,
Just a quickie. We are planning an upgrade from 7.1.3 to 7.3. Since we
have to bring down our production server to do it we are planning on
killing all the birds with one shot. We are running RH 7.1 and were
planning on using RH 8. After reading a little bit recently here and
there and insta
