Tom Lane wrote:
Scott Shattuck <[EMAIL PROTECTED]> writes:
Willing to learn here but skipping a vacuum full has caused some issues
for us. Here's some data from a recent 3 day test run that was done with
regular vacuums but not vacuum fulls. When running with vacuum full the
ind
Tom Lane wrote:
Scott Shattuck <[EMAIL PROTECTED]> writes:
Robert Treat wrote:
I don't think this is entirely true. On tables that have large numbers
of inserts, but no updates or deletes, you do not need to run vacuum.
In my experience I've seen tables with numerous ind
VACUUM ANALYZE must be used.
again, great work Philip.
Robert Treat
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ss
Scott Shattuck
Tec
pful.
Thanks in advance!
ss
Scott Shattuck
Technical Pursuit Inc.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
QL with respect
at all times, keeping in mind that we communicate with them not only
through this forum, but through the code we write for them.
As a personal note, any time I see a response to my posts consisting of
"Why would you want to do that?" I automatically assume the auth
evel...but I can say that it
would be significant to my customer(s) and my ability to recommend PG to
future "ex-Oracle users" ;) to see a fix make it into the 7.3 final.
ss
Scott Shattuck
Technical Pursuit Inc.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Wed, 2002-09-04 at 22:49, Tom Lane wrote:
> Scott Shattuck <[EMAIL PROTECTED]> writes:
> > ... I don't understand why an exclusive table-level lock is being
> > taken out to add a trigger.
>
> Well, that's a schema change; it makes sense to me to forbid ac
On Wed, 2002-09-04 at 15:51, Stephan Szabo wrote:
>
> On 4 Sep 2002, Scott Shattuck wrote:
>
> > Under what conditions would the following statement cause the USERS
> > table to lock out selects?
> >
> >
> > alter table my_coupons
> > a
Hi,
Under what conditions would the following statement cause the USERS
table to lock out selects?
alter table my_coupons
add constraint FK_mc_user_id
FOREIGN KEY (mc_frn_user_id)
REFERENCES users(user_ID);
ss
Scott Shattuck
Technical Pursuit Inc.
---(end
On Tue, 2002-08-13 at 22:42, Tom Lane wrote:
> Scott Shattuck <[EMAIL PROTECTED]> writes:
> > I'm seeing the following error about once a week or so:
> > 2002-08-13 12:37:28 [24313] FATAL 1: LWLockAcquire: can't wait without
> > a PROC structure
>
>
A couple of admin nice-to-have's based on the last few weeks of 24x7
operation are:
Allow DBA/Database Owner to log in even when max_connections has been
reached so they can determine which queries are hung via
pg_stat_activity etc. and perform any other needed work to restore
stability.
Log off
ur query.
Ouch!
Any idea what's going on here? Is the LWLockAcquire related to something
like the size of the lock table or something? Any help on eliminating
this error would be appreciated. Thanks!
ss
Scott Shattuck
Technical Pursuit Inc.
---(end of broadcast)-
On Tue, 2002-08-13 at 19:54, Christopher Kings-Lynne wrote:
> > I'm finding it hard to visualize situations where I'd want the extra
> > baggage of pg_dump for something like this. If I want the schema at
> > all, I'll probably want it separate from the data so that I can hack
> > the schema conv
Hi,
We recently put up a new 7.2.1 installation on Solaris 8 that serves a
24x7 e-commerce site. The system seems to run pretty well most of the
time but we see a consistent form of performance anomaly.
Watching pg_stat_activity the system spends most of it's time running
smoothly with queries c
How about a SOAP interface and a web-based front end that provides the cross
platform support? My company's TIBET framework would provide a solid
foundation for this kind of admin suite. In fact, we're already in the
planning stages on doing just that.
ss
Scott Shattuck
Technical P
and use interfaces
they're familiar with is more our goal. Something like a DBI module that
would function as if you were external to PG even though you aren't. Write a
stored proc as if it were going to run outside of the database. Install it
inside when it makes sense. No code change.
hope you
understand we're in a somewhat interesting position with some time and $ to
focus on PG, particularly as it relates to replication/recovery issues. Any
guidance on how we can put that to work for the community would be
appreciated.
Thanks.
ss
Scott Shattuck
Technical Pursuit Inc.
17 matches
Mail list logo