Hi,
I'm trying to introduce myself into postgresql development and I'm working on
the "tablespace for temporary objects and sort files" TODO item. The attached
patch shows what I've already done. The GUC is currently
called "temp_tablespaces".
The tablespace changes correctly for me when crea
How about this patch?
Of course, it might be a rare case that such check is necessary...
Toru SHIMOGAKI wrote:
> The following bug has been logged online:
>
> Bug reference: 2704
> Logged by: Toru SHIMOGAKI
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Ope
I just set up to build with MSVC on a brand new box, and came across a
couple of more fixes:
* New versions of OpenSSL come with proper debug versions, and uses
suffixed names on the LIBs for that. Adapts library handling to deal
with that.
* Fixes error where it incorrectly enabled Kerberos base
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> I would've liked to give freezing a new opcode,
> but we've ran out of them (see htup.h).
Hardly ... we have plenty of unused rmgr id's still.
The real issue that still has to be resolved is the interaction of all
this stuff with PITR scenarios
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> I prepared patch which use oid output function instead regproc output.
> This change works only for COPY TO command.
This is not a bug and we're not going to fix it, most especially not
like that.
regards, tom lane
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Hmm, maybe it should be using regprocedure instead?
Not unless you want to break initdb. The only reason regproc still
exists, really, is to accommodate loading of pg_type during initdb.
Guess what: we can't do type lookup at that poi
Heikki Linnakangas wrote:
> Here's a patch for WAL logging tuple freezes in vacuum, per discussion
> on pgsql-bugs.
>
> This patch is against CVS head. Should this be backported to stable
> branches? I think it should.
Keep in mind that previous releases do not use the same method for
determining
Here's a patch for WAL logging tuple freezes in vacuum, per discussion
on pgsql-bugs.
This patch is against CVS head. Should this be backported to stable
branches? I think it should.
After writing the patch, I realized that it needs some thought if
backported, because WAL records of removing tu