Is it possible to achieve your goals by using things like
"delete * from table1 where id!=stuffIwant" instead of dropping it?
Yes, I think I better use delete statements instead of drop statements
knowing PostgreSQL can't always handle drop/rename statements in
transactions correctly.
Jaco de
Mike Mascari wrote:
From an otherwise EXTREMELY happy user :-) (full smile...), I see 3
scenarios:
(1) Disallow DDL statements in transactions
(2) Send NOTICE's asking for the user to not trigger the bug until the bugs
can be fixed -or-
(3) Have all DDL statements implicity commit any
I'd like to be able to find a book title that contain C++ in the
title
select * from books where title ~* 'C++' doesn't work.
I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...
Any hints would be most appreciated
Thanks...
Bill Sneed,
Hi,
Perhaps this is useful for the FAQ as it was very difficult for me to
discover...
To increase shared mem and semaphores on BSDI
(courtesy of Sin'ichiro Miyatani on bsdi-users list)
In /usr/src/sys/sys/sem.h,
#ifndef SEMMNI
#define SEMMNI 10 /* # of semaphore identifiers */
On Sat, 27 Nov 1999, Jason C. Leach wrote:
hi,
I've read that a few of you are putting email into a postgres DB. I'd
be interested in doing something similar. Would any of you care to
share the secret that allows sendmail to deposit the email to a db, or
how you get it from
Hi,
I could really use some help understanding where exactly the limits are in
my use of memory and how postgres uses memory.
I am running PostgreSQL 6.4 on BSDI 3.0 with 64M ram and 262M virtmem.
table sessions is 74M and 371K records
isfiji= explain select user_name from sessions;
NOTICE:
I understand Oracle 8i does something like this (also acting as an FTP
backend).
You might want to scower their site for good ideas
Darvin Zuch
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Howie
Sent: Sunday, November 28, 1999 3:39 PM
To: Jason C.
Bill Sneed wrote:
I'd like to be able to find a book title that contain C++ in the
title
select * from books where title ~* 'C++' doesn't work.
I've tried all the basic methods of quoting the Plus (+) signs but
none seem to work...
Any hints would be most appreciated
if PostgreSQL could successfully rollback DDL statements sanely (and thus
diverge from ORACLE). I guess I don't expect that to happen successfully
until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index names and their
Bruce Momjian wrote:
if PostgreSQL could successfully rollback DDL statements sanely (and thus
diverge from ORACLE). I guess I don't expect that to happen successfully
until
something the equivalent of TABLESPACES is implemented and there is a
disassociation between table names, index
Vadim Mikheev wrote:
Bruce Momjian wrote:
if PostgreSQL could successfully rollback DDL statements sanely (and
thus
diverge from ORACLE). I guess I don't expect that to happen
successfully
until
something the equivalent of TABLESPACES is implemented and there is a
At 05:11 PM 11/29/99 +1200, John Henderson wrote:
snippage
Here are the questions...
1) Can someone explain how postgreSQL uses memory so that I can understand
what I should be doing here.
BTW, I am running postgres with -B 884. Can someone also explain how
postgres uses shared mem so that I
I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to get
Mike Mascari wrote:
Will that aid in fixing a problem such as this:
session 1:
CREATE TABLE example1(value int4);
BEGIN;
session 2:
BEGIN;
ALTER TABLE example1 RENAME TO example2;
session 1:
INSERT INTO example1 VALUES (1);
END;
NOTICE: Abort Transaction and not in
Bruce Momjian wrote:
I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read pg_class to
Bruce Momjian wrote:
I have to say that I'm going to change on-disk database/table/index
file names to _OID_! This is required by WAL because of inside of
log records there will be just database/table/index oids, not names,
and after crash recovery will not be able to read
16 matches
Mail list logo
