Hm ... seems like that requires more special cases, not fewer.
What I was imagining was the current database-local pg_description plus
a single shared table pg_shared_description. When you add more kinds of
shared objects (SQL roles maybe?) obj_description doesn't need to
change...
Oh yeah,
-Original Message-
From: [EMAIL PROTECTED] on behalf of Bruce Momjian
Sent: Sat 6/19/2004 4:18 AM
To: PostgreSQL-development
Subject: [HACKERS] Twelve days to feature freeze
Win32 - need service manger code,
Claudio posted a patch for that that looked OK. I haven't had a chance
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Sat 6/19/2004 12:21 AM
To: Dave Page
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Cannot initdb in cvs tip
The target block number is obviously broken :-(. But maybe you have
a build consistency problem ---
Any change someone who knows (or who can declare that we not fix
existing dumps) comment on this?
Chris
Christopher Kings-Lynne wrote:
I think this is wrong, primarily because it's gonna be seriously
incompatible with existing dump files. The existing technique is
that each TOC entry says who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've made a fresh checkout from CVS and getting the following error.
Platform is RHEL 3 with
[EMAIL PROTECTED] pgsql]$ gcc -v
...
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
Bruce Momjian wrote:
Actually, this is the current state of this issue.
Right, please comment on this. To recall, it uses shared memory for a
switch to next logfile name flag, which can't cause harm in case of
shmem corruption, and a postmaster opened filehandle (kept open) to a
dummy file
Devrim GUNDUZ wrote:
==
Below are the relevant lines in
/home/pgsql75/pgsql/src/interfaces/libpq/Makefile:
==
ifeq ($(PTHREAD_H_WIN32))
pthread.h : % :
It seems ALTER TABLE does not support table space. I think this is
neccessary because:
1) if a data disk if full, users need to move table to another table
spaces.
2) if performance hits, users could move the table which is likely a
bottle neck to another table space.
I know that
The new verion of pgpool, yet another open source replication software
for PostgreSQL is now in RC1:
ftp://ftp.sra.co.jp/pub/cmd/postgres/pgpool/pgpool-2.0RC1.tar.gz
pgpool is a single master/query based/synchronous replication
server. It acts as a proxy server between PostgreSQL client and
On Sat, 19 Jun 2004, Tatsuo Ishii wrote:
It seems ALTER TABLE does not support table space. I think this is
neccessary because:
1) if a data disk if full, users need to move table to another table
spaces.
2) if performance hits, users could move the table which is likely a
bottle
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I am still hopeful that we can get a significant plperl improvement before
feature freeze, including shared data space, set returning funcs,
composite returning funcs, triggers and an spi query mechanism. It will be
touch and go and we
Fix applied. Sorry.
---
Andreas Pflug wrote:
Devrim GUNDUZ wrote:
==
Below are the relevant lines in
On Fri, Jun 18, 2004 at 19:21:07 -0600,
Scott Marlowe [EMAIL PROTECTED] wrote:
On Fri, 2004-06-18 at 08:24, Chris Browne wrote:
Santo Quartarone [EMAIL PROTECTED] writes:
What's the safest email browser?
less is pretty safe, more or less ;-).
You didn't specify what sort of
[ switching to pghackers for wider comment ]
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
By the way, I think that we should deny users the ability to create
tablespaces that begin with pg_. Also, the existing ones should be
pg_global and pg_default. That way, we have room to move if
Tom Lane wrote:
[ switching to pghackers for wider comment ]
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
By the way, I think that we should deny users the ability to create
tablespaces that begin with pg_. Also, the existing ones should be
pg_global and pg_default. That way, we have
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 19 June 2004 00:22
To: Dave Page
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Cannot initdb in cvs tip
Dave Page [EMAIL PROTECTED] writes:
I'm getting the following error when trying to initdb with CVS
Tom Lane wrote:
Although DROP TABLESPACE can detect tables existing in the target
tablespace, it doesn't have any way to detect schemas that reference
that tablespace as their default tablespace. Thus you can get
implementation-level failures like this one:
$ mkdir /tmp/junk
regression=# create
Gaetano Mendola [EMAIL PROTECTED] writes:
is there no dependencies between these two objects.
No, and there's little point in adding one, since it wouldn't prevent
the problem from happening if you issue the DROP TABLESPACE from a
different database.
regards, tom lane
I think this is another on of those 'might be Win32 specific' problems.
When building on XP, with OpenSSL 0.9.7c (from the bitWalk MinGW tools),
I get the following failure:
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../src/include
Andreas Pflug [EMAIL PROTECTED] writes:
I could think of cases where temporary schemas should go to a different
tablespace, but AFAICS since these are created implicitely there's no
way to redirect them. Maybe an additional attribute in pg_database for a
default temp tablespace is
On Sat, 19 Jun 2004, Tom Lane wrote:
[ switching to pghackers for wider comment ]
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
By the way, I think that we should deny users the ability to create
tablespaces that begin with pg_. Also, the existing ones should be
pg_global and
On Sun, 2004-06-20 at 08:04, Dave Page wrote:
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 19 June 2004 00:22
To: Dave Page
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Cannot initdb in cvs tip
Dave Page [EMAIL PROTECTED] writes:
I'm
22 matches
Mail list logo
