Just wondering what is the status of this patch. Is seems from comments
that people like the idea. I have also looked in the archives for other
people looking for this kind of feature and have found alot of interest.
If you think it is a good idea for 7.2, let me know what needs to be
On Saturday 15 September 2001 03:03, Jim Buttafuoco wrote:
Just wondering what is the status of this patch. Is seems from comments
that people like the idea. I have also looked in the archives for other
people looking for this kind of feature and have found alot of interest.
Can we have a
Sorry, I forgot to repost in hackers.
Stephan Szabo wrote:
We are running into a situation where psql is aborting the transaction
when one call returns an error. Is there a way to continue on with
transaction or at least save what has already happened (like an Oracle
Save Point)?
Vadim,
I guess I am still confused...
In dbcommands.c resolve_alt_dbpath() takes the db oid as a argument.
This number is used to find the directory where the data files live.
All the patch does is put the indexes into a db oid_index directory
instead of db oid
This is for tables
Can you explain how I would get the tblNode for an existing database
index files if it doesn't have the same OID as the database entry in
pg_databases.
Well, keeping in mind future tablespace implementation I would
add tblNode to pg_class and in pg_databases I'd have
defaultTblNode and
Yes that is exactly what I am going to do for 7.3 (had trouble adding
tblNode to pg_class so I stopped for now...)
Can you explain how I would get the tblNode for an existing database
index files if it doesn't have the same OID as the database entry
in
pg_databases.
Well, keeping in
just curious, is there any reason why a plperl RPM package isn't included
with the official distribution (from postgres website)?
No incredible deal just to build it myself, just wondering.
-rchit
---(end of broadcast)---
TIP 5: Have you checked
Hi,
In addition to this, Joel Burton's paper regarding Hacking the
Referential Integrity tables gives very good insight into how to find
out exactly what you're looking for, and the final example of SQL code
at the end of the article will work as is :
Got it upgraded on the cvsup.postgresql.org server ... still have to do
the other servers ...
On Wed, 12 Sep 2001, Thomas Lockhart wrote:
New problems with CVSup. We should all upgrade asap, though I'm not sure
of the current status of builds for non-FreeBSD machines. Marc, could we
This patch warns about oid/xid wraparound during VACUUM. Apply the part
people consider appropriate. I may not be around before beta.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive,
Bruce Momjian [EMAIL PROTECTED] writes:
This patch warns about oid/xid wraparound during VACUUM. Apply the part
people consider appropriate. I may not be around before beta.
None of it is appropriate anymore...
regards, tom lane
---(end of
Bruce Momjian [EMAIL PROTECTED] writes:
This patch warns about oid/xid wraparound during VACUUM. Apply the part
people consider appropriate. I may not be around before beta.
None of it is appropriate anymore...
OID wraparound isn't a problem?
--
Bruce Momjian
Bruce Momjian [EMAIL PROTECTED] writes:
None of it is appropriate anymore...
OID wraparound isn't a problem?
Well, it could be a problem if an app is relying on uniqueness of OIDs
without having installed an unique index on OIDs. However, I do not
think it is the business of the backend to
13 matches
Mail list logo
