Well, I'll answer your questions and help you a little too, or at least
try...
* Alvaro Herrera in "[GENERAL] Does this table exist?" dated 2000/11/02
* 17:44 wrote:
> Now, I'm building a database to hold customer data that needs to be
> organized in a one-table-per-customer manner. No, I don't
n
rgt + (droprgt - droplft + 1)
when (rgt > droprgt) and (rgt < newpos) then
rgt - (droprgt - droplft + 1)
else rgt end;
end;
' language 'plpgsql';
--
ashley clark
PGP signature
* Tom Lane in "Re: [GENERAL] Can this be done?" dated 2000/11/15 00:42
* wrote:
> Ashley Clark <[EMAIL PROTECTED]> writes:
> > Can I defer constraint checking on unique indexes?
>
> No, not at present. Consider restructuring your UPDATE into
> sequential ste
* Frank Miles in "[GENERAL] newbie debugging pl/pgsql : better way?"
* dated 2000/10/24 11:56 wrote:
> I have a simple function that isn't working. I've enabled debugging,
> but the error message is still mystifying. My function is as
> follows:
>
>
> CREATE FUNCTION proj_name
I've come up with this example and I want to know why it does what it
does.
-- snip --
You are now connected to database template1.
CREATE DATABASE
You are now connected to database testing.
psql:test2.sql:11: NOTICE: CREATE TABLE/UNIQUE will create implicit
index 'subdivs_name_key' for table 's
ame from builders where name like 'A%' or name
like 'B%';
NOTICE: QUERY PLAN:
Index Scan using builders_name_key, builders_name_key on builders
(cost=0.00..10.25 rows=16 width=12)
EXPLAIN
Does the similarity of these numbers to the first ones above have any
significance or is it just c
Maybe someone will know what's going on here.
I'm running 7.1 and vacuuming the db regularly at 4am each day. But
these last few days as it vacuums it hangs reaping dead processes.
2001-05-04 04:00:09 [27285] DEBUG: --Relation personnel--
2001-05-04 04:00:09 [27285] DEBUG: Pages 0: Changed 0
* Tom Lane in "Re: VACUUM is hanging" dated 2001/05/04 22:05 wrote:
> > I also seem to have found the culprit. I have Apache::DBI set up
> > and it's holding something open. Restarting Apache let the vacuum
> > finish normally.
>
> Try not to leave open transactions hanging around in your Apache
Occasionally and without warning I get this from my daily vacuum
cronjob:
NOTICE: RegisterSharedInvalid: SI buffer overflow
NOTICE: InvalidateSharedInvalid: cache state reset
I don't understand what these mean. Should I be concerned about them
and what do they signify?
--
creaky halls
PGP
