On Thu, 4 Jul 2002, Tom Lane wrote:
> Curt Sampson <[EMAIL PROTECTED]> writes:
> > Shared memory pages, IIRC, are locked, meaning that they cannot be
> > swapped.
>
> Is that really how it works on *BSD? That's great if so --- it's
> exactly what Postgres
On Wed, 27 Aug 2003, Tom Lane wrote:
> Curt Sampson <[EMAIL PROTECTED]> writes:
> > While we're at it, anybody got a clue on how to reindex system tables?
> The procedure given in the REINDEX reference page doesn't work for you?
You mean with the standalone backend?
ts out around
a few megabytes, and doesn't take too long to grow to several hundred
megabytes.)
So far, the only way I've found to fix this is to do a complete dump
and reload of the database, but that's a pain since we have tables with
mutual constraints that can't be reload
0 (zero).
> I dont know how to interpret that. What does
> it mean.
It means you haven't done an ANALYZE after changing the size of the
database.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.NetBSD.org
these purposes). Try doing an ANALYZE.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
---(end of broadcast)---
TIP 5: Have you
for retreiving stuff older than that and for off-site
backups.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
you could always shut down both databases and
rsync one to the other.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
---(end of broadcast)--
I recommend somehow replicating the data from the OLTP server
to another server for the OLAP folks.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
-
ck, keep a separate list of changes to the block that any
other processes must also examine, and only apply those changes to the
block after the WAL entry is confirmed written to stable storage.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don&#
GB of data, since the number of blocks buffered
will not be limited by the maximum address space of a single process.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
---
;ll want to check with
EXPLAIN that you're still getting the same query plan.
But I don't think this is true of every view, just some of them.
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we
C... What's the sysctl setting I use
> to set/check the data size limits?
It's not a sysctl, because those limits are settable per-process.
Use "ulimit -aS" to check the current (soft) limits, and "ulimit
-aH" to check the hard limits (beyond which the soft
w many you get? If you know you want to
do a table scan if you have more than, say, 500 rows that match
'W%', you'd only have to read a few index pages to determine whether
or not there are more than 500 rows, right?
Or am I on crack here?
cjs
--
Curt Sampson <[EMAIL PROTECTED
er products in that
class being worthwhile. An SQL Server installation is typically a
$10,000-$50,000 kind of thing. (You can do it for a lot less, but
most such products that can get by with such small installations
would probably be just as well off with PostgreSQL.)
14 matches
Mail list logo
