[EMAIL PROTECTED] writes:
> [postgres@localhost postgres]$ ipcrm shm 4224672
> shmctl : Identifier removed
> [postgres@localhost postgres]$ ipcs -m 4224672
> ((returns a ton of addr info))
The old postmaster may be gone, but what about child backends? I don't
think the shm segment will go away
Jeff Waugh, <[EMAIL PROTECTED]>, clued me in...
I was mis-reading this:
> If you're sure there are no old backends still running,
> remove the shared memory block with ipcrm(1), or just
> delete "/var/lib/pgsql/data/postmaster.pid".
I was trying to delete the pid in the above file, it no longer
NetBSD 1.5 on i386
PostgreSQL 7.1.1 and 7.1.2
I downloaded source, compiled and installed Postgresql 7.1.1 and all was well.
Once the NetBSD pkgsrc packages caught up with the latest distribution, I decided to
use it to install and maintain PG. So, I deleted /usr/local/pgsql and installed us
> Am I correct that with no UNDO in 7.1.X, we should only be keeping one
> WAL file around, or maybe two?
Not necessarily. How much do you do between checkpoints?
But yeah, there's no reason to save data further back than one or maybe
two checkpoints, as long as UNDO isn't there.
> As the person who wrote it :) It was my understanding that PostgreSQL
> stores large objects on the filesystem outside of the database tables.
Definitely not true.
I think that was once an available option, many years ago ... but
it's not there now.
> could someone please describe the actual
I had a system, that was running postgres-7.1-1, lockup, and I had to
reboot. Since the reboot, I can't get postgresql restarted.
As user 'postgres':
[postgres@localhost postgres]$ date
Thu May 31 00:40:09 PDT 2001
((current date))
[postgres@localhost postgres]$ echo $PGDATA
/var/lib/pgsql/da
Doug McNaught <[EMAIL PROTECTED]> writes:
> Good article. The only inaccuracy I saw was that he claims Postgres'
> storage of large objects is "in the filesystem" and "inefficient".
He may be thinking about the fact that Postgres used to store each large
object as a separate table, which did ind
Hello,
Heh... I wrote that :)
J
On Sat, 2 Jun 2001, Michael wrote:
> http://www.zend.com/zend/art/databases.php
>
> Needless to say Postgresql comes out looking pretty good. Good to have
> links like this to show the advantages of Postgresql when I'm trying to
> convert others to using it.
>
>
Steve Wampler <[EMAIL PROTECTED]> writes:
> Are the WAL segment files the ones located in pg_xlog?
Right, the ones with sixteen-hex-digit filenames. Sorry for not being
perfectly clear.
regards, tom lane
---(end of broadcast)-
Steve Wampler <[EMAIL PROTECTED]> writes:
> FATAL 2: ZeroFill(/var/lib/pgsql/data/pg_xlog/xlogtemp.16747) failed: No such file
>or directory
The error message is bogus --- almost certainly, the real problem is not
enough free space to create another 16-MB WAL segment. (I have a TODO
item about
http://www.zend.com/zend/art/databases.php
Needless to say Postgresql comes out looking pretty good. Good to have
links like this to show the advantages of Postgresql when I'm trying to
convert others to using it.
---(end of broadcast)---
TIP 2: yo
I had postgresql die this morning because of lack of disk space
on /var (base grew to 422MB fairly quickly, and I'm not sure why
yet... pg_xlog is at 16450.
So, I thought I go in and look at some table sizes to try and
figure out what's so large, but I can't restart postmaster to
look at the tab
> "d" == drevil <[EMAIL PROTECTED]> writes:
d> way to check for this condition before I do the addition? Is there a
d> way to put a constraint on a variable, such that it's always positive?
I have bunches of these:
pid integer CHECK (pid >= 0),
They work great. Your update will return
> This is precisely what I am looking for.
> Who wants to type in a huge list of tables?
> Not me. Also I'm not qualified to make
> these changes myself.
Apart from the referential inegrity problem, you can get the table
names with
SELECT relname FROM pg_class WHERE relname NOT LIKE 'pg
The table definition is:
CREATE TABLE ADDRESS (
GROUPID INTEGER NOT NULL,
ADDRESSID INTEGER NOT NULL,
NAME VARCHAR(256) NOT NULL,
SURNAME VARCHAR(256) NOT NULL,
ADDRESS VARCHAR(256),
PHONE VARCHAR(256),
EMAIL VARCHAR(256),
FAX
Denis Gasparin <[EMAIL PROTECTED]> writes:
> All the operations are perfomed in the same table with 1.000.000 of records
> and the searches (those specified by the WHERE clause of SELECT and UPDATE)
> are done only on the primary key of the table itself.
Have you checked (with EXPLAIN) that you
Hi to all!
I'm doing some benchmarks to test Interbase vs PostgreSQL. The
test are done with the respective PHP client. The two servers are installed
on the same machine with RedHat 7.0.
Pgsql has been started with these configuration options:
- sort_mem = 512
- fsync
Hello community,
I have a doubt about multiple access to a table in my database.
When two people are accessing the same table for insert or update,
is the affected row locked or am I supposed to lock this row explicit
in my application???
Any help will by welcome! :)
Best Regards / Un saludo /
On Wed, 30 May 2001 12:54:17 -0400, [EMAIL PROTECTED] wrote:
> On Wed, May 30, 2001 at 04:02:51PM +0100, Peter Haworth wrote:
> > On Wed, 30 May 2001 08:07:11 -0400, [EMAIL PROTECTED] wrote:
> > The new behaviour is mre correct.
> >
>
> Why? The old behavior is better. Less coding.
It's also
It's just me that's receiving all this majordomo errors or it's the
whole list?
--- Forwarded message follows ---
Date sent: Thu, 31 May 2001 12:34:23 -0400 (EDT)
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject:Maj
Hi,
In the Advanced Features section.
In the section about Inheritance, there is the following command:
INSERT INTO dist_author(a_id, lastname, email, award)
VALUES (110, 'Seuss','[EMAIL PROTECTED]',
'National Book Awards);
There is a quote (') missing, it should read:
INSERT INTO dist_author(
21 matches
Mail list logo
