On Tue, 24 Aug 2004 00:39:55 -0400, Tom Lane [EMAIL PROTECTED] said:
Shinji Teragaito [EMAIL PROTECTED] writes:
I made a patch to let PostgreSQL work in the LP64 data model on
HP-UX PA-RISC and HP-UX Itanium platform.
The s_lock change looks good ... but ...
This patch seems likely to
Yep, related. There was a typo in win32.h for lstat that was exposed by
the new tablespace changes. I also added the proper parameters rather
than just redefining the symbol.
Attached is the patch. Do we need to repackage beta2 for this? Tom did
ask for Win32 testers two days ago and it is
Tom,
Still having problems. This is the output of make check. I am going to compile
with debug symbols and try to
attach with gdb next. any other ideas?
Thanks
Jim
-
Running in noclean mode.
I just fixed a bug that caused Win32 to fail to compile. Do we want to
repackage beta2? Of course we still don't even know if the new
tablespace code works on Win32 because someone tried compiling it only
today.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL
Fabien COELHO [EMAIL PROTECTED] writes:
The sequences are in the same tablespace as the system catalogs of the
database they are in, so this objection is moot.
three (unusual?) commands to reach the moot state:
psql CREATE TABLESPACE foo LOCATION '/tmp/postgres';
psql CREATE
Dear Tom,
psql CREATE TABLE bla.boo(id SERIAL PRIMARY KEY);
Now you have schema bla, table bla.boo, index bla.boo_pkey and sequence
bla.boo_id_seq all in tablespace foo.
Hmm, that's a bug.
If you consider that a bug, then you can also add: CREATE SEQUENCE bla.sg;
The intention
Hi!
I'm new to PostgreSQL (and C) and what I'm trying to do is to store a
query plan on disc (in a binary file).
My approach is to use SPI functions to get the query plan and then
transform it into a 'storable' format (Replacing the pointers with
actual values).
Is there any other way to do
Hello,
If you are a newbie :) I would suggest taking a slightly simpler
approach by using prepared queries. Prepared queries will give you the
stored plan, albeit per connection.
E.g:
PREPARE FOO AS SELECT
EXECUTE FOO;
Sincerely,
Joshua D. Drake
Katsaros Kwn/nos wrote:
Hi!
I'm new to
Fabien COELHO wrote:
Dear Tom,
psql CREATE TABLE bla.boo(id SERIAL PRIMARY KEY);
Now you have schema bla, table bla.boo, index bla.boo_pkey and sequence
bla.boo_id_seq all in tablespace foo.
Hmm, that's a bug.
If you consider that a bug, then you can also add: CREATE
As of CVS tip, an increase in a USERLIMIT parameter in postgresql.conf
will be enforced against the sessions of superusers as well as everyone
else. That's because I ifdef'd out this code:
/*
* If user is a superuser, he gets to keep his setting. We can't check
* this unless
Hello,
Just poking around to see if anyone is working on resurrecting the concept
of pg_upgrade after all these years? If not, I think I have nearly ready a
high-level design of how the whole upgrade procedure will work, but I just
need to clear out some ideas and put them together in a
Quoting Bruce Momjian [EMAIL PROTECTED]:
Yep, related. There was a typo in win32.h for lstat that was exposed by
the new tablespace changes. I also added the proper parameters rather
than just redefining the symbol.
Attached is the patch. Do we need to repackage beta2 for this? Tom did
Andrew,
If I were loony enough to want to make an attempt at a version updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system catalog changes exist anywhere? Any really gross
problems immediately
present
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system catalog changes exist anywhere? Any really gross
Marc,
Slony is not an upgrade utility, and falls short in one big case ..
literally .. a very large database with limited cash resources to
duplicate it (as far as hardware is concerned). In small shops, or those
with 'free budget', Slony is perfect ... but if you are in an organization
Now you have schema bla, table bla.boo, index bla.boo_pkey and sequence
bla.boo_id_seq all in tablespace foo. ISTM that tablespace foo cannot be
removed without hand-fixing pg_catalog and hand-moving files or links in
the database directory.
Hmmm, I wonder why the tablespace is set to the foo
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where to
poke first? Does a
catalog/list of system
Tom Lane wrote:
As of CVS tip, an increase in a USERLIMIT parameter in postgresql.conf
will be enforced against the sessions of superusers as well as everyone
else. That's because I ifdef'd out this code:
/*
* If user is a superuser, he gets to keep his setting. We can't check
On 8/31/2004 9:38 PM, Andrew Rawnsley wrote:
On Aug 31, 2004, at 6:23 PM, Marc G. Fournier wrote:
On Tue, 31 Aug 2004, Josh Berkus wrote:
Andrew,
If I were loony enough to want to make an attempt at a version
updater
(i.e. migrate a
7.4 database to 8.0 without an initdb), any suggestions on where
Is it possible to test for plperl and add some plperl tests to the
regression suite?
I see the pg_regress installs and runs with_perl=no.
The problem is that cygwin postgres builds and runs fine, only the perl
extensions fails (IPC problem when loading the huge perl dll).
So I really would
20 matches
Mail list logo
