Hello,
It's come to our attention that in 14-16 days our OID's will wrap around and
we need some advice. We're running 7.3.5 in our current production and plan
to eventually move to 7.4.6 which we have in testing. Production consists
of one database cluster with 26 databases. All tables are cre
"Spiegelberg, Greg" <[EMAIL PROTECTED]> writes:
> It's come to our attention that in 14-16 days our OID's will wrap around and
> we need some advice.
Are you actually using the OIDs for anything? If not, don't worry about
it.
Unless you are actually depending on OIDs to be unique in some of your
Tom Lane wrote:
"Spiegelberg, Greg" <[EMAIL PROTECTED]> writes:
It's come to our attention that in 14-16 days our OID's will wrap around and
we need some advice.
Are you actually using the OIDs for anything? If not, don't worry about
it.
We use OID's to store files in the database. Does that qua
Greg Spiegelberg <[EMAIL PROTECTED]> writes:
> I read a mailing list article from a while back and there was mentioned in
> it the possibility of OID's becoming a INT8. Does this exist in any of the
> new versions?
Don't hold your breath.
Exactly how are you "using OIDs to store files"? Do you
Tom Lane wrote:
Exactly how are you "using OIDs to store files"? Do you mean you're
using large objects?
The table is
Table "public.imgs"
Column | Type | Modifiers
--++--
id
I have a function defined in my own library (.lib) that updates a table of
logged information about
the start and end times, return codes, etc. of etl, backup, and other such
processes.
The function uses an existing connection to the DB and writes a new record
to that log table.
void UpdateLog
Greg Spiegelberg <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Exactly how are you "using OIDs to store files"? Do you mean you're
>> using large objects?
> The table is
> Table "public.imgs"
>Column | Type | Modifiers
> --+-
Tom Lane wrote:
Well, put a unique index on the contents column. Better to fail an
insert than to get a conflict of LO OIDs.
Can't do that. Our app won't handle it.
If you were on 7.4 or later you could do ALTER TABLE SET WITHOUT OIDS so
you'd not be sucking up OIDs for the table rows themselves
Greg Spiegelberg <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Well, put a unique index on the contents column. Better to fail an
>> insert than to get a conflict of LO OIDs.
> Can't do that. Our app won't handle it.
Actually, I think the lo_import() will fail anyway, whether you like it
or
Hi everyone, I'm new to PostgreSQL administration. I hope the people
here will have some ideas to help me out.
My current situation is that I am moving my database across machines
without access to network. It would be possible, but more difficult to
install a network.
I understand that the recom
Geoffrey Ducharme wrote:
Hi everyone, I'm new to PostgreSQL administration. I hope the people
here will have some ideas to help me out.
My current situation is that I am moving my database across machines
without access to network. It would be possible, but more difficult to
install a network.
I un
Thanks for the tip. I tried logging in as the service and I managed to
shut down the service.
I also saw how I had originally misconfigured the system. Since not
all accounts are stored in the same place, I had to dig in a little
deeper to grab the old, wrong account. From there, reinstalling
Post
12 matches
Mail list logo
