Josh Berkus <[EMAIL PROTECTED]> writes:
> Historically, the only way to troubleshoot some of the contrib modules
> was to e-mail the author. If people think that we've reached a standard
> that everything in /contrib is now well-documented and supported by the
> general community, the I suppose
Tom,
If we do want to keep credits in the SGML pages, how extensive should
they be? I already took it on myself to remove Gene Selkov's snailmail
address, but do we even want email addresses there? A lot of them are
probably dead, and the ones that aren't are causing their owners to get
extra
David Fetter wrote:
balanced
gradual
extended (I see you mention time-extended but wouldn't time be implicit
based on the actual docs and thus we only need extended?)
How about "smoothed?"
perhaps we should call it Jacob checkpointing, then.
cheers
andrew
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 6 Dec 2007 19:43:29 -0800
David Fetter <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 06, 2007 at 07:19:44PM -0800, Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Thu, 06 Dec 2007 20:44:49 -0500
> > Tom Lane
On Thu, Dec 06, 2007 at 07:19:44PM -0800, Joshua D. Drake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 06 Dec 2007 20:44:49 -0500
> Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > Am I the only one who finds the phrase "distribute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 06 Dec 2007 20:44:49 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Am I the only one who finds the phrase "distributed checkpointing"
> > a bit awkward? Would it be better if we used "time-distribu
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Well, if we want to cram all that stuff in there, how shall we do it?
>> It seems wrong to put all those lines into one text field, but I'm
>> not sure I want to add six more text fields to the CSV format
>> either. Thoughts?
> Reall
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Am I the only one who finds the phrase "distributed checkpointing" a bit
> awkward? Would it be better if we used "time-distributed checkpointing"
> instead?
Yeah, "distributed" has a bunch of connotations that are wrong for this
purpose.
I spent a bi
Gregory Stark <[EMAIL PROTECTED]> writes:
> Oh, I bet it's not the enum which is 8 bytes but that the time_t required
> 8-byte alignment so there's 4 bytes of padding before it.
That makes more sense --- I was having a hard time imagining why anyone
would need 64-bit enums, let alone why that woul
Hi,
It seems pgindent is not considering EXEC_BACKEND typedefs. For
example,
static void restore_backend_variables(BackendParameters * param, Port *port);
BackendParameters is not considered a typedef.
Not sure how serious an issue this is ... I just noticed and thought I
would mention it.
--
Gregory Stark wrote:
>The looming problem is that you won't be able to use any libraries or 3rd
>party tools which use time_t in their interface unless you build with the same
>size time_t as they do. I don't know how're expected to find out that a .so
>you're handed has a different size time_t.
"Rainer Bauer" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>
>>This is because of (at least) two changes in the ABI between the runtimes used
>>by mingw and VC++.
>> 1) Enums are apparently 8 bytes on VC++ but 4 bytes on mingw
>
> They are 4 bytes here on my 32 bit WinXP machine with VS2005
Gregory Stark wrote:
>This is because of (at least) two changes in the ABI between the runtimes used
>by mingw and VC++.
> 1) Enums are apparently 8 bytes on VC++ but 4 bytes on mingw
They are 4 bytes here on my 32 bit WinXP machine with VS2005SP1.
> 2) time_t is 8 bytes on VC++ but 4 bytes on m
Am I the only one who finds the phrase "distributed checkpointing" a bit
awkward? Would it be better if we used "time-distributed checkpointing"
instead?
The phrase is used in the release notes, but it's not used anywhere in
the main docs.
--
Alvaro Herrera http://www.amazon.com
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I can't see any very good reason for text logs to have different
content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
Guillaume Lelarge wrote:
> Tom Lane a écrit :
> > Guillaume Lelarge <[EMAIL PROTECTED]> writes:
> >> I try to answer a simple question : what happens when I do a simple
> >> "INSERT" on a just started PostgreSQL server.
> >
> >> From what I understand with the INSERT statement, here is what happen
Tom Lane a écrit :
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>> I try to answer a simple question : what happens when I do a simple
>> "INSERT" on a just started PostgreSQL server.
>
>> From what I understand with the INSERT statement, here is what happens :
>> * backend loads first (and on
On Thu, 2007-12-06 at 13:22 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
> >> To preserve platform and version independence of the dump.
>
> > Only if there is a risk. Since a common route to upgrade is a
> > dump/restore b
FYI, I am traveling to Japan, leaving this Saturday, and returning
Wednesday, December 19. I will be visiting companies and attending a
Japan PostgreSQL Users Group (JPUG) cruise on December 18.
I will be less responsive to email during this period but promise to be
all caught-up by the time we a
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
>> To preserve platform and version independence of the dump.
> Only if there is a risk. Since a common route to upgrade is a
> dump/restore back onto same box it seems worth having an option to do
> this.
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I can't see any very good reason for text logs to have different
> content from CSV logs.
Well, if we want to cram all that stuff in there, how shall we do it?
It seems wrong to put all those lines into one text field, but I'm
not sure I want to add si
Tom Lane wrote:
"depesz" <[EMAIL PROTECTED]> writes:
Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was intenti
On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Is there a reason why pg_dump avoids using BINARY mode COPY?
>
> To preserve platform and version independence of the dump.
OK, thats what I guessed.
> > Unless there is a specific reason not to we c
Tom Lane wrote:
> "depesz" <[EMAIL PROTECTED]> writes:
> > Description:csvlog skips some logs
>
> The point here is that CSV-format log output doesn't include the
> DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
> you might get with normal output.
>
> I suppose this was int
Simon Riggs <[EMAIL PROTECTED]> writes:
> Is there a reason why pg_dump avoids using BINARY mode COPY?
To preserve platform and version independence of the dump.
> Unless there is a specific reason not to we could/should allow an option
> on the dump.
Is there any evidence to show that there'd b
On Thu, Dec 06, 2007 at 05:30:02PM +, Simon Riggs wrote:
> Is there a reason why pg_dump avoids using BINARY mode COPY?
> (Or am I missing something?)
>
> Unless there is a specific reason not to we could/should allow an option
> on the dump.
Probably because BINARY dumps arn't portable. Just
Is there a reason why pg_dump avoids using BINARY mode COPY?
(Or am I missing something?)
Unless there is a specific reason not to we could/should allow an option
on the dump.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)--
"depesz" <[EMAIL PROTECTED]> writes:
> Description:csvlog skips some logs
The point here is that CSV-format log output doesn't include the
DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
you might get with normal output.
I suppose this was intentional in order to keep the CS
Guillaume Lelarge <[EMAIL PROTECTED]> writes:
> I try to answer a simple question : what happens when I do a simple
> "INSERT" on a just started PostgreSQL server.
> From what I understand with the INSERT statement, here is what happens :
> * backend loads first (and only) block from footable fil
On Dec 5, 2007 8:58 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> If we do want to keep credits in the SGML pages, how extensive should
> they be?
...
> I don't have a strong opinion one way or the other, except that I think
> we should have a uniform policy for all the contrib modules.
One of the
Joshua D. Drake wrote:
Manolo _ wrote:
./configure --enable-debug --enable-cassert --enable-depend
You don't want --enable-cassert on a production machine it is a
performance hit.
He's clearly not setting up for production, but for development, where
cassert is quite appropriate.
Manolo _ wrote:
>
> I'm trying to compile PG on Ubuntu in order to hack tuplesort.c code
> I just downloaded and unpacked the source code and red README and INSTALL
> files.
>
> I'm going to
>
> ./configure --enable-debug --enable-cassert --enable-depend
>
> then I would
>
> make
> make insta
Manolo _ wrote:
I'm trying to compile PG on Ubuntu in order to hack tuplesort.c code
I just downloaded and unpacked the source code and red README and INSTALL files.
I'm going to
./configure --enable-debug --enable-cassert --enable-depend
then I would
make
make install
Can I improve somethin
Gregory Stark wrote:
> This is because of (at least) two changes in the ABI between the runtimes used
> by mingw and VC++. 1) Enums are apparently 8 bytes on VC++ but 4 bytes on
> mingw and 2) time_t is 8 bytes on VC++ but 4 bytes on mingw.
For the record:
Mingw
=
WARNING: sizeof(ControlFil
In trying to run a benchmark comparing mingw with VC++ builds Dave discovered
that if you initdb with one and try to run with the other you get a message
saying "incorrect checksum in control file" rather than the more appropriate
and friendly "database files are incompatible with server".
This i
I'm trying to compile PG on Ubuntu in order to hack tuplesort.c code
I just downloaded and unpacked the source code and red README and INSTALL files.
I'm going to
./configure --enable-debug --enable-cassert --enable-depend
then I would
make
make install
Can I improve something adding some mis
On Dec 6, 2007 5:26 PM, srinath narra <[EMAIL PROTECTED]> wrote:
> hi,
>
> when i connecting my postgresql which giving
> org.postgresql.util.PSQLException: ERROR: conversion between UNICODE and
> MULE_INTERNAL is not supported.please send solution about this problem.
>
> Srinath
>
postgre
hi,
when i connecting my postgresql which giving
org.postgresql.util.PSQLException: ERROR: conversion between UNICODE and
MULE_INTERNAL is not supported.please send solution about this problem.
Srinath
On Wed, Dec 05, 2007 at 10:46:51PM -0800, Joshua D. Drake wrote:
> Tom Lane wrote:
> >As of CVS HEAD, some of the contrib module documentation pages have
> >extensive credit screeds, eg
> >http://developer.postgresql.org/pgdocs/postgres/cube.html
> >and some just have the author's name, with or wit
39 matches
Mail list logo
