On 10/25/06, Jaime Casanova <[EMAIL PROTECTED]> wrote:
On 10/24/06, Albert Cervera Areny <[EMAIL PROTECTED]> wrote:
> I'm trying to introduce myself into postgresql development and I'm working on
> the "tablespace for temporary objects and sort files" TODO item.
Now, PG_TEMP_FILES_DIR seems to
I sent this in a while back, but never heard anything about it.
This patch makes psql's \lo_* commands respect the -q flag (or other
methods of setting quiet mode) as well as HTML output mode. This came in
very handy when writing a regression test which uses the \lo_import
command since it would
Neil Conway <[EMAIL PROTECTED]> writes:
> Note that this patch breaks the translations of these strings, so I
> haven't applied it yet. Should I apply it now, or wait for 8.3 to
> branch?
BTW, unless Peter says it's OK, my advice is to wait. It's already
likely to be the case that translation upd
On 10/26/06, Gregory Stark <[EMAIL PROTECTED]> wrote:
I think what you want is to add a new method entry in pg_type to
allow a type to declare a method to tell you whether a change
is work-free or not. Then any type, even user-defined types,
can allow some changes to be work-free and some not wit
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
>
> True, so VARCHAR seems like the only one? That's the only one I've
> really encountered in
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
> True, so VARCHAR seems like the only one? That's the only one I've
> really encountered in th
On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
This makes some really quite unacceptable assumptions about
the meaning and encoding of typmod ...
True, so VARCHAR seems like the only one? That's the only one I've
really encountered in the field on a fairly regular basis.
I'm also wondering
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> The attached patch handles the simple case where a user wants to
> increase the user-defined storage size of a variable length object,
> such as VARCHAR or NUMERIC, without having to rebuild the table.
This makes some really quite unacceptable assump
The attached patch handles the simple case where a user wants to
increase the user-defined storage size of a variable length object,
such as VARCHAR or NUMERIC, without having to rebuild the table.
It does so by verifying that no transform was defined and testing
whether the user simply requested
Neil Conway <[EMAIL PROTECTED]> writes:
> BTW, should pre_auth_delay be included in SHOW ALL?
It's really just a debug aid, so I wouldn't complain if SHOW ALL didn't
show it.
regards, tom lane
---(end of broadcast)---
TIP 3:
This patch makes the short_desc and extra_desc fields of the GUC table
more consistent: both text in both fields should be complete sentences
that begin with a capital letter and end in a period.
Note that this patch breaks the translations of these strings, so I
haven't applied it yet. Should I a
Alvaro Herrera napsal(a):
Zdenek Kotala wrote:
Tom Lane napsal(a):
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
Dave Page wrote:
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> > Sent: 26 October 2006 14:19
> > To: Albert Cervera Areny
> > Cc: pgsql-patches@postgresql.org
> > Subject: Re: [PATCHES] Tablespace for temporary objects
Zdenek Kotala wrote:
> Tom Lane napsal(a):
> >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 tha
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 26 October 2006 14:37
> To: [EMAIL PROTECTED]
> Cc: Dave Page; Albert Cervera Areny; pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] Tablespace for temporary objects and sort files
>
> bruce wrote:
> > D
bruce wrote:
> Dave Page wrote:
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> > > Sent: 26 October 2006 14:19
> > > To: Albert Cervera Areny
> > > Cc: pgsql-patches@postgresql.org
> > > Subject: Re: [PATCHES]
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> Sent: 26 October 2006 14:19
> To: Albert Cervera Areny
> Cc: pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] Tablespace for temporary objects and sort files
>
>
> This has bee
Tom Lane napsal(a):
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.
OK, The behavior of regproc type i
This has been saved for the 8.3 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Albert Cervera Areny wrote:
> Sorry about the wrong diff format. Attached is the good one.
>
> A Dimecres 25 Octubre
19 matches
Mail list logo
