On Tue, Apr 29, 2014 at 10:22 AM, Steve Clark wrote:
> We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb
> twice a day (originally started with 7.3.x). Can anybody see a reason why we
> need to
> continue to do this?
I used to re-index regularly with earlier 6.x and 7.x
On 04/29/2014 07:22 AM, Steve Clark wrote:
Hello,
We have a small (2GB) 8.4.20 database. The prior maintainer ran a
reindexdb
twice a day (originally started with 7.3.x). Can anybody see a reason
why we need to
continue to do this?
I don't. It certainly appears to be a piece of duct-tape pu
Hello,
We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb
twice a day (originally started with 7.3.x). Can anybody see a reason why we
need to
continue to do this?
Thanks,
--
Stephen Clark
*NetWolves Managed Services, LLC.*
Director of Technology
Phone: 813-579-3200
F
On Mar 10, 8:57 pm, [EMAIL PROTECTED] (Tom Lane) wrote:
> [EMAIL PROTECTED] writes:
> > I am trying to reindex some indexes through a batch script. for
> > example
> > Database : hermes
> > Schema : sc1
> > Indexes : ind1
> > when i use reindexdb with the following switches
> > ./reindexdb --inde
[EMAIL PROTECTED] writes:
> I am trying to reindex some indexes through a batch script. for
> example
> Database : hermes
> Schema : sc1
> Indexes : ind1
> when i use reindexdb with the following switches
> ./reindexdb --index=ind1 hermes
> i get the below error message
> reindexdb: reindexing
I am trying to reindex some indexes through a batch script. for
example
Database : hermes
Schema : sc1
Indexes : ind1
when i use reindexdb with the following switches
./reindexdb --index=ind1 hermes
i get the below error message
reindexdb: reindexing of index "ind1" in database "hermes" fa
Hi!
For the past two days I've been getting the following errors from my cron
scripts which connect to the database:
day 1, on a SELECT statement:
ERROR: could not open relation 1663/35154/221872: No such file or directory
day 2, on a LOCK TABLE statement:
ERROR: could not open relation 1663
David Wall <[EMAIL PROTECTED]> writes:
> Thanks, Robert. Actually, I noted that each time I ran my backup
> script, the OID mentioned in the error was bigger than previous number.
That's fairly interesting, but can you provide a self-contained test
case? The reindexdb script really doesn't do a
It really isn't neccessary. That said, there is *something* going on with your
db, so it might be prudent to figure out what it is.
Thanks, Robert. Actually, I noted that each time I ran my backup
script, the OID mentioned in the error was bigger than previous number.
Before I run the re
On Thursday 25 May 2006 19:34, David Wall wrote:
> Rats! I found nothing But just for grins, I ran the reindexdb
> program a second time, and this time it reported a different OID, higher
> than the previous. I know we didn't change the template1 database other
> than using it when creating
Rats! I found nothing But just for grins, I ran the reindexdb
program a second time, and this time it reported a different OID,
higher than the previous. I know we didn't change the template1
database other than using it when creating new databases, creating
users, tablespaces, etc.
My
David,
On Thu, May 25, 2006 at 02:07:27PM -0700, David Wall wrote:
> >object. Look in template1 and see if you see a table with that OID.
> Thanks, but I clearly lack that expertise. How do I find "a table with
> that OID"?
Do a normal select against pg_class. Something like:
select oid, rel
(repost to newsgroup since the other went directly to Mr. Lane's email
address)
I think you've done something to template1,
even though you say you
haven't. Out-of-the-box, an 8.1.3 database won't have any OIDs
assigned
above about 11000, so OID 41675 would have to belong to a user-crea
David Wall <[EMAIL PROTECTED]> writes:
> When I create a brand new database and then run the reindexdb program
> under PG 8.1.3, I get the follow error:
> reindexdb: reindexing of database "" failed: ERROR: could not open
> relation with OID 41675
> I'm not sure what this error is since we
When I create a brand new database and then run the reindexdb program
under PG 8.1.3, I get the follow error:
reindexdb: reindexing of database "" failed: ERROR: could not open
relation with OID 41675
I'm not sure what this error is since we have not even added any data
yet. Is this so
Thank you Tom. I will look at reindexing the database
---(end of broadcast)---
TIP 6: explain analyze is your friend
"Carlos Oliva" <[EMAIL PROTECTED]> writes:
> In the mean time maybe I can ask you: Does VACUUM FULL ANALYZE of a
> database would also reindex the user indexes of a database? I am trying to
> eliminate index bloating.
VACUUM FULL not only doesn't do a REINDEX for you, it's more likely to
bloat t
12:01 PM
To: Carlos Oliva
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Reindexdb
Carlos Oliva wrote:
> Hi Joshua,
> I think that it was installed from a RedHat distribution and the
> installation left out reindexdb from the contrib folder. I will look into
> this.
>
>
]
[mailto:[EMAIL PROTECTED] On Behalf Of Joshua D. Drake
Sent: Thursday, May 11, 2006 11:27 AM
To: Carlos Oliva
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Reindexdb
Carlos Oliva wrote:
-->
Hi,
Where can I find information about installing and running
contrib/reindexdb? I h
trying to
eliminate index bloating.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joshua D. Drake
Sent: Thursday, May 11, 2006 11:27 AM
To: Carlos Oliva
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Reindexdb
Carlos Oliva wrote:
> -->
&
Carlos Oliva wrote:
-->
Hi,
Where can I find information about installing and running
contrib/reindexdb? I have searched the manuals and appendixes without
much luck. I just know that there is a contrib for reindexing an entire
database.
We run postgresql (v 7.4.x) in Linux RedHat.
Hi,
Where can I find information about installing and
running contrib/reindexdb? I have searched the manuals and appendixes without
much luck. I just know that there is a contrib for reindexing an entire
database.
We run postgresql (v 7.4.x) in Linux RedHat.
On Mar 7, 2006, at 8:06 PM, David Wall wrote:
I've upgraded from 8.0 to 8.1 and want to be sure I'm making the
changes that are required.
For my backups, I have removed the option --blobs because it says
this is no longer needed. I guess the backup automatically
includes blobs now?
You
I've upgraded from 8.0 to 8.1 and want to be sure I'm making the changes
that are required.
For my backups, I have removed the option --blobs because it says this
is no longer needed. I guess the backup automatically includes blobs now?
I have also been running the contributed 'reindexdb' sc
24 matches
Mail list logo
