On Mon, Mar 06, 2006 at 12:06:28AM -0500, Bruce Momjian wrote:
> Is there any progress on this cleanup?
I'm still planning to work on it unless somebody else wants to, but
I was hoping for more feedback on the use of DROP TYPE CASCADE.
That seems to be the only way to remove a type due to the circ
On Sun, 2006-03-05 at 15:15 -0500, Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> > samples %symbol name
> > 24915704 96.2170 ltsReleaseBlock
> > 3872651.4955 LogicalTapeRead
> > 1687250.6516 inlineApplySortFunction
>
> Hmm ... the comment in ltsReleaseBlo
Is there any progress on this cleanup?
---
Michael Fuhr wrote:
> On Thu, Mar 02, 2006 at 02:49:13PM -0500, Tom Lane wrote:
> > Michael Fuhr <[EMAIL PROTECTED]> writes:
> > > Would it make sense for DROP TYPE to have some kin
On Sat, Mar 04, 2006 at 01:07:15PM -0500, [EMAIL PROTECTED] wrote:
> For me, I prefer the interactive behaviour of ZSH. Multiline
> statements remain as multiline statements, as they were typed.
> One can navigate up and down through the multiline statement
> to make alterations. The real beauty of
On Thu, Mar 02, 2006 at 06:16:00AM -0800, [EMAIL PROTECTED] wrote:
> > TRUNCATE is another command that takes an access exclusive lock.
>
> The whole SP takes about 10 seconds to run total. The TRUNCATE command
> only takes less than a second. However, the access exclusive lock is
> held through
Tom Lane wrote:
> SQL92 contains a construct "table1 UNION JOIN table2", which is defined
> essentially the same as "table1 FULL JOIN table2 ON false" --- you get
> all the rows of table1 null-extended into the table2 columns, and all
> the rows of table2 null-extended into the table1 columns, and
"Markus Bertheau" <[EMAIL PROTECTED]> writes:
> SIGHUP_handler() calls ProcessConfigFile() which calls
> ParseConfigFile() which reads postgresql.conf.
> For me that means that postgresql.conf in read in the signal handler,
> which contradicts the claim in the README. Where's my error?
The commen
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Was there ever a decision in "the libcurl thread"?
No, not yet.
Personally I'm unconvinced that we should depend on libcurl: if it's
going to use openldap to do LDAP work, then the only good reason to use
libcurl rather than openldap directly is if
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> samples %symbol name
> 24915704 96.2170 ltsReleaseBlock
> 3872651.4955 LogicalTapeRead
> 1687250.6516 inlineApplySortFunction
Hmm ... the comment in ltsReleaseBlock sez
/*
* Insert blocknum into array, preserving decr
Hi,
src/backend/utils/misc/README says
"
If SIGHUP is received, the GUC code rereads the postgresql.conf
configuration file (this does not happen in the signal handler, but at
next return to main loop; note that it can be executed while within a
transaction).
"
SIGHUP_handler() calls ProcessConf
SQL92 contains a construct "table1 UNION JOIN table2", which is defined
essentially the same as "table1 FULL JOIN table2 ON false" --- you get
all the rows of table1 null-extended into the table2 columns, and all
the rows of table2 null-extended into the table1 columns, and no actual
join rows.
SQ
Markus Bertheau wrote:
> Hi,
>
> What's the status of the TODO item
>
> "Allow commenting of variables in postgresql.conf to restore them to defaults
> Currently, if a variable is commented out, it keeps the previous
> uncommented value until a server restarted."
>
> I take that to apply to the
Hi,
What's the status of the TODO item
"Allow commenting of variables in postgresql.conf to restore them to defaults
Currently, if a variable is commented out, it keeps the previous
uncommented value until a server restarted."
I take that to apply to the configuration re-read at SIGHUP?
Markus
Tom Lane wrote:
> Bruce Momjian writes:
> > The file is /src/tools/copyright. We don't re-run it for minor releases
> > because there are almost no changes in minor releases. If we did run
> > it, it would change a lot of code for little purpose.
>
> It might make sense to run it once a year in
Bruce Momjian writes:
> The file is /src/tools/copyright. We don't re-run it for minor releases
> because there are almost no changes in minor releases. If we did run
> it, it would change a lot of code for little purpose.
It might make sense to run it once a year in early January, rather than
On Sun, Mar 05, 2006 at 05:13:11PM +, Pierre Racine wrote:
> Hi,
>
> I have develop my own data type and my own operators on this data type. I
> could not find how to tell PostgreSQL which precedence I want to assign to
> my operator. For example, I want my unary operator "~" to have a highe
Hi,
I have develop my own data type and my own operators on this data type. I
could not find how to tell PostgreSQL which precedence I want to assign to
my operator. For example, I want my unary operator "~" to have a higher
precedence than my "+" operator. For now I have to use parenthesis to
On Sun, Mar 05, 2006 at 09:54:02PM +0800, Christopher Kings-Lynne wrote:
> contrib/vacuumlo perhaps?
vacuumlo only calls lo_unlink(); the data still exists in pg_largeobject
due to MVCC.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you che
Hi,
what's the status of this todo item? The relevant thread from 2001 is here:
http://archives.postgresql.org/pgsql-hackers/2001-10/thrd6.php#00011
> I think we should
> leave the code alone, and instead document in 7.2 that -o is deprecated
> (and explain what to do instead), with the intentio
I have updated the copyrights on all the files in CVS HEAD, and updated
the script that does the work. The commit message was too long to be
automatically accepted.
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can
[EMAIL PROTECTED] wrote:
> On Sun, Mar 05, 2006 at 12:02:19PM +0100, Matteo Beccati wrote:
> > >After all - you wouldn't want somebody to say that PostgreSQL copied
> > >them, because the date was later, would you? :-)
> > I think it won't be hard to understand what "Copyright (c) 1996-2006"
> > m
contrib/vacuumlo perhaps?
Michael Fuhr wrote:
On Sat, Mar 04, 2006 at 12:08:52PM +0530, Md.Abdul Aziz wrote:
I am a presently working on a module which enhances postgre to
store audio files,while storing the aduido file in the databese i used
liod,now the problem is i am able to unlink but st
On Sun, Mar 05, 2006 at 12:02:19PM +0100, Matteo Beccati wrote:
> >After all - you wouldn't want somebody to say that PostgreSQL copied
> >them, because the date was later, would you? :-)
> I think it won't be hard to understand what "Copyright (c) 1996-2006"
> means ;)
Maybe... but if it hasn't
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>
forgot to mention that this is 8.1.3 compiled from source.
>>>
>>>See the discussion starting here:
>>>http://archives.postgresql.org/pgsql-hackers/2006-02/msg00590.php
>
>
>>I was following this thread - and it was partly
Mark,
After all - you wouldn't want somebody to say that PostgreSQL copied
them, because the date was later, would you? :-)
I think it won't be hard to understand what "Copyright (c) 1996-2006"
means ;)
Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com
--
25 matches
Mail list logo
