Would it be possible to offer an option for the OID column to get its value
from an int4 primary key (settable on a per table basis maybe)?
- Stuart
-Original Message-
From: Hiroshi Inoue [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, July 21, 2001 7:31 AM
To: Zeugswetter Andreas SB
Cc:
Sean Chittenden wrote:
Has anyone here thought about using the spread libraries for WAL
replication amongst mutliple hosts? With this library I think it'd be
possible to have a multi-master replication system..
Yes, there is some work being done to use Spread as the group
- Original Message -
From: eCommerce Software
Solutions Inc.
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, July 21, 2001 9:15 PM
Subject: Leaking Handles in Postgres 7.1.2 on Cygwin dll 1.3.2 on
Win 2000
The situation is this:I have cygwin
with ( dll 1.3.2 ) and
We are evaluating PostgreSQL for a possible port to our
proprietary hardware platform. The hardware is a very
high end (processing power, I/O throughput, storage capacity)
storage system, attached to a host machine running Windows2K.
The question is what's the right way to do it. The following
I'd like to have statistics on when my database was last backed up or
vacuumed. Currently, I'm implementing this by using simple shell
scripts that write a date stamp to ascii files. I was wondering
whether this is or could be a feature added to Postgres?
For example, could one of the pg_*
I'm trying create a unique index using more than one field and
applying a function in one field to achieve case insensitive
uniqueness but postgresql doesn't accept.
create table a(
id int primary key,
id2 int not null,
name varchar(50),
unique(id2, lower(name))
);
"Henshall, Stuart - WCP" wrote:
Would it be possible to offer an option for the OID column to get its value
from an int4 primary key (settable on a per table basis maybe)?
- Stuart
Sorry I don't understand well what you mean.
What kind of advantages are there if we let OIDs be optional
and
Hi there,
I remember that in earlier versions of Postgres.
You have to do something (which I cannnot remember) to enable
a user to create plpgsql functions.
which versions of postgres were they?
thanks in advance.
Bill
--
The mark of a good
Bill Shui wrote:
Hi there,
I remember that in earlier versions of Postgres.
You have to do something (which I cannnot remember) to enable
a user to create plpgsql functions.
which versions of postgres were they?
thanks in advance.
Bill
CREATELANG as
When I delete a table that has an OID, the OID does not get deleted
correct? How can I delete the data from the large object?
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
What I mean is, do host lookups first in the text file, then if a
pg_hostaccess table (example) exists, check it for host entries. This
alleviates HUP or restart etc. to reload a config file.
David
Bruce Momjian wrote:
I haven't heard of any more issues with pg_hba.conf so I will mark the
What I mean is, do host lookups first in the text file, then if a
pg_hostaccess table (example) exists, check it for host entries. This
alleviates HUP or restart etc. to reload a config file.
Can't do that. Postmaster has no database access. Must be fast.
--
Bruce Momjian
August Zajonc wrote:
Perhaps Postgresql folks could start thinking of peace talk sites as well? I
recommand the tropics. Then all that's left is to find something to fight
about to justify a flight down to paradise.
You are all welcome here in Cyprus. Monty too, he will find a lot of
Swedish
Domingo Alvarez Duarte wrote:
I'm trying create a unique index using more than one field and
applying a function in one field to achieve case insensitive
uniqueness but postgresql doesn't accept.
create table a(
id int primary key,
id2 int not null,
name varchar(50),
Tom Lane wrote:
Steve Howe [EMAIL PROTECTED] writes:
..\..\backend\lib\dllist.c(20) : fatal error C1083: Cannot open include
file: 'sysexits.h': No such file or directory
Jan added that recently. I was wondering if it was portable or not ...
looks like now we know :-(.
Grmbl - tell
[EMAIL PROTECTED] (Lamar Owen) wrote in message
news:[EMAIL PROTECTED]...
[trimmed cc:list]
On Wednesday 18 July 2001 17:09, Bruce Momjian wrote:
OK, we need to vote on whether Oid's are optional, and whether we can
have them not created by default.
[All the below IMHO]
OID's
I'm trying create a unique index using more than one field and
applying a function in one field to achieve case insensitive
uniqueness but postgresql doesn't accept.
create table a(
id int primary key,
id2 int not null,
name varchar(50),
unique(id2, lower(name))
);
Anyone have an
Tom Lane wrote:
Patrick Macdonald [EMAIL PROTECTED] writes:
I understand your solution is for the existing architecture which does
not support point-in-time recovery. If this item is picked up, your
solution will become a stumbling block due the above mentioned log
extent deletions.
Tom,
What you are describing is a pseudo circular log. Other database
systems (such as DB2) support the concept of both circular and
recoverable logs. Recoverable is named this way because
recoverable logs can be used in point-in-time recovery. Both
methods support crash recovery.
In
Tom Lane wrote:
and then the code takes care of swallowing expressions until ';',
similarly to the way SQL commands are handled. (plpgsql's parsing
methodology is sinfully ugly, isn't it? But I don't suppose you
want to try to replace it...)
It is, indeed, and I'm sorry for that.
From: Jan Wieck [EMAIL PROTECTED]
Tom Lane wrote:
and then the code takes care of swallowing expressions until ';',
similarly to the way SQL commands are handled. (plpgsql's parsing
methodology is sinfully ugly, isn't it? But I don't suppose you
want to try to replace it...)
It
Try this:
test=# create table test (a int4);
CREATE
test=# grant select, update on te
Stop there and press 'TAB' to complete the word 'test'.
Your command line then gets rewritten to :
grant select, update on SET
It seems that it occurs when you have commas in there...
Chris
22 matches
Mail list logo
