Am Dienstag, 12. Juli 2005 05:29 schrieb Bruce Momjian:
Bruce Momjian wrote:
I have heavily modified your patch and have applied it. Instead of
using langinfo, I used a \pset variable numericsep.
Because I don't have langinfo on my system, so I can't test it, nor add
configure code for
On Mon, Jul 11, 2005 at 04:47:18PM -0700, Kris Jurka wrote:
Marko Kreen wrote:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dragonflydt=2005-07-11%2003:30:04
Linking problem with zlib on Solaris 9/x86. I am clueless about
this. I can anyone look into it?
It appears to be
In the latest HEAD, a PL/Perl function that returns a list value
instead of a reference causes a segmentation fault:
CREATE FUNCTION foo() RETURNS integer[] AS $$
return (1, 2, 3, 4);
$$ LANGUAGE plperl;
SELECT foo();
server closed the connection unexpectedly
Here's the stack trace:
#0
Where in the source is the decision about the placement new tuple (on
which page to put it) made ?
I'd like to take a look at adding gravity to that decision, do that I
can make postgres to decide to place new tuple (inserted or updated)
near the beginning of file, in order to make it possible
On L, 2005-07-09 at 16:50 -0400, Alvaro Herrera wrote:
On Sat, Jul 09, 2005 at 11:43:52PM +0300, Hannu Krosing wrote:
Could the new file not be made to cover the next available 1GB of file
space, that is a new physical file ?
This could made using of same kind of machinery my proposal
Hi,
Are there C++ APIs
that enable data in postgres database to be extracted in xml format?
Rgds
Bhanu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There are many commits to back branches and 8.0 branch since the last dot
releases were announced.
Any plans for new releases before 8.1beta1?
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
On Tue, Jul 12, 2005 at 04:30:04PM +0300, Hannu Krosing wrote:
Where in the source is the decision about the placement new tuple (on
which page to put it) made ?
heap_insert and heap_update. They get a page with free space from the
FSM, or extend the relation, or --in heap_update case-- try
Hannu Krosing [EMAIL PROTECTED] writes:
Where in the source is the decision about the placement new tuple (on
which page to put it) made ?
RelationGetBufferForTuple() and the free space map
src/backend/access/heap/hio.c
src/backend/storage/freespace/freespace.c
I'd like to take a look at
Peter Eisentraut wrote:
Am Dienstag, 12. Juli 2005 05:29 schrieb Bruce Momjian:
Bruce Momjian wrote:
I have heavily modified your patch and have applied it. Instead of
using langinfo, I used a \pset variable numericsep.
Because I don't have langinfo on my system, so I can't test
Bruce Momjian pgman@candle.pha.pa.us writes:
We do allow MDY and DMY specification, but that controls both input and
output in the server, while this just controls psql display. It is a
good question how other settings should be handled, but I don't know the
answers. Anyone?
This patch
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
We do allow MDY and DMY specification, but that controls both input and
output in the server, while this just controls psql display. It is a
good question how other settings should be handled, but I don't know the
answers.
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
This patch sounds quite a lot different from what I thought we had
agreed to, which was a way to specify that the client-side LC_NUMERIC
locale settings should be used for formatting numbers. I think the only
pset should be locale
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Tom Lane wrote:
This patch sounds quite a lot different from what I thought we had
agreed to, which was a way to specify that the client-side LC_NUMERIC
locale settings should be used for formatting numbers. I think the only
Hannu Krosing [EMAIL PROTECTED] writes:
I try to state my reworked idea of concurrent indexing in a more clear
way:
The index build in done 2 transactions, need one new type of lock and a
new system column in pg_class to tell planner not to use an incomplete
index. This similar to vacuum in
Bruce Momjian pgman@candle.pha.pa.us writes:
Ah, I see this now in our code:
CurrentLocaleConv.decimal_point = strdup(extlconv-decimal_point);
CurrentLocaleConv.grouping = strdup(extlconv-grouping);
CurrentLocaleConv.thousands_sep = strdup(extlconv-thousands_sep);
Is this what
On Tue, Jul 12, 2005 at 10:48:40AM -0400, Bruce Momjian wrote:
Peter Eisentraut wrote:
Am Dienstag, 12. Juli 2005 05:29 schrieb Bruce Momjian:
Bruce Momjian wrote:
The current state allows users to manually set the format, or
actually only one aspect of the format? Where can you set
On Tue, Jul 12, 2005 at 16:30:48 +0300,
Devrim GUNDUZ [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There are many commits to back branches and 8.0 branch since the last dot
releases were announced.
Any plans for new releases before 8.1beta1?
I seem
On Sat, Jul 09, 2005 at 11:48:35AM -0400, Tom Lane wrote:
Stephen Frost [EMAIL PROTECTED] writes:
* Mike Mascari (mascarm@mascari.com) wrote:
And when the transaction that issued the TRUNCATE aborts after step 3,
but newer transactions commit?
The newer transactions would have to check
As I mentioned in the last post to a thread in general detailing some of the hurdles of attempting to set up PostgreSQL virtual hosting, we've had to hack pg_dump to achieve the behavior that we want.The modifications we made call into question (for us, anyway) a few design decisions in PostgreSQL
Should we add the multibyte regression tests to the buildfarm test
suite? Does anyone know how portable they are? I guess adding them would
be one way to find out.
cheers
andrew
---(end of broadcast)---
TIP 9: In versions below 8.0, the
If you're going to do this I would suggest keeping in mind that a
similar tactic could be used to help keep a table clustered (I think
there may even be a TODO on that). The basic idea there is to use the
clustering index to decide the best page to put a tuple on and try and
return that page (or
On Tue, 12 Jul 2005, Marko Kreen wrote:
On Mon, Jul 11, 2005 at 04:47:18PM -0700, Kris Jurka wrote:
Marko Kreen wrote:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dragonflydt=2005-07-11%2003:30:04
Linking problem with zlib on Solaris 9/x86. I am clueless about
this. I can
Michael Fuhr wrote:
In the latest HEAD, a PL/Perl function that returns a list value
instead of a reference causes a segmentation fault:
CREATE FUNCTION foo() RETURNS integer[] AS $$
return (1, 2, 3, 4);
$$ LANGUAGE plperl;
SELECT foo();
server closed the connection unexpectedly
Here's the
Thomas F. O'Connell [EMAIL PROTECTED] writes:
Our first attempt to get things working was to remove all calls to
selectSourceSchema. Clearly, this is playing with fire,
No, it's breaking it entirely; and so would your proposed change.
The reason for the restrictive search path is to ensure that
On Tue, Jul 12, 2005 at 02:59:37PM -0400, Andrew Dunstan wrote:
Note that all plperl functions are called in scalar context, and it is
always wrong to return a list (as opposed to a listref). In fact, the
value received might surprise you even if it worked (it would be the
value of the
Alvaro Herrera wrote:
On Tue, Jul 12, 2005 at 02:59:37PM -0400, Andrew Dunstan wrote:
Note that all plperl functions are called in scalar context, and it is
always wrong to return a list (as opposed to a listref). In fact, the
value received might surprise you even if it worked (it
I'm starting to get results with dbt2 on a 4-way opteron system and
wanted to share what I've got so far since people have told me in the
past that this architecture is more interesting than the itanium2 that
I've been using.
This 4-way has 8GB of memory and four Adaptec 2200s controllers
Seems like down mail server ate first mail.
Here it is again.
On Tue, Jul 12, 2005 at 12:51:44PM +0300, Marko Kreen wrote:
Hopefully the last regression failure.
- openssl.c used EVP_MAX_KEY_LENGTH / EVP_MAX_IV_LENGTH
constants for buffers, which are small in case of
OpenSSL 0.9.6x
Hopefully the last regression failure.
- openssl.c used EVP_MAX_KEY_LENGTH / EVP_MAX_IV_LENGTH
constants for buffers, which are small in case of
OpenSSL 0.9.6x and internal AES. (I tested it with
0.9.7 only, so I didn't notice...)
- Also I noticed that the wrapper macros for CBC mode
do
Marko Kreen marko@l-t.ee writes:
Hopefully the last regression failure.
- openssl.c used EVP_MAX_KEY_LENGTH / EVP_MAX_IV_LENGTH
constants for buffers, which are small in case of
OpenSSL 0.9.6x and internal AES. (I tested it with
0.9.7 only, so I didn't notice...)
- Also I noticed
Andrew Dunstan [EMAIL PROTECTED] writes:
Michael Fuhr wrote:
In the latest HEAD, a PL/Perl function that returns a list value
instead of a reference causes a segmentation fault:
Patch below fixes the SEGV, and you will see instead:
Applied, thanks.
regards, tom lane
On Tue, Jul 12, 2005 at 03:45:55PM -0400, Andrew Dunstan wrote:
Alvaro Herrera wrote:
On Tue, Jul 12, 2005 at 02:59:37PM -0400, Andrew Dunstan wrote:
Note that all plperl functions are called in scalar context, and
it is always wrong to return a list (as opposed to a listref). In
Hi all,
I examined the effect of block-hole compression patch.
I compared the amounts of writing of the WAL data of CVS(7/11) and
8.0.3. (The amount of the WAL data writing was measured by the number of
executions of the write() function in XLogWrite().)
And, I measured the size of the hole.
Could we please get this patch applied? It seems like the right thing to do.
cheers
andrew
Jim C. Nasby wrote:
On Tue, Jul 05, 2005 at 10:09:19PM +0200, Peter Eisentraut wrote:
I wrote:
So either we code up some intelligence to put the C in the right
position or we have to pass
On Mon, 2005-07-11 at 12:38 -0700, Joshua D. Drake wrote:
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
What do you guys think of having a vacuum summary command? E.g.;
VACUUM [FULL] [ANALYZE] SUMMARY
... that will turn SUMMARY into a fully reserved word ...
Simon Riggs [EMAIL PROTECTED] writes:
On Mon, 2005-07-11 at 12:38 -0700, Joshua D. Drake wrote:
What do you guys think of having a vacuum summary command? E.g.;
How about putting this in the logfile, without any command changes?
Actually, tying it to VACUUM might not have been such a great
It'd be relatively easy I think to extract the current FSM statistics
in a function that could be invoked separately from VACUUM. Not sure
how we ought to return 'em though --- the VACUUM way of a bunch of INFO
messages is a bit old-fashioned. Maybe a statistics view?
That would work for
Hi Mark,
Great stuff. One of the things that led me to PostgreSQL a couple years
back was the exceptional OLTP performance I was able to wring out of it
when running my own internal benchmarks against it.
I have a couple questions (that I apologize if they are answered
elsewhere). Note that
David Fetter wrote:
On Tue, Jul 12, 2005 at 03:45:55PM -0400, Andrew Dunstan wrote:
In perl, if there is any ambiguity it is the called function that is
responsible for checking, not the caller. See perldoc -f
wantarray. PLPerl explicitly passed G_SCALAR as a flag on all
calls to plperl
On Tue, Jul 12, 2005 at 02:59:37PM -0400, Andrew Dunstan wrote:
Note that all plperl functions are called in scalar context, and it is
always wrong to return a list (as opposed to a listref). In fact, the
value received might surprise you even if it worked (it would be the
value of the
Patch applied. Thanks.
---
Peter Eisentraut wrote:
I wrote:
So either we code up some intelligence to put the C in the right
position or we have to pass down A B and D separately from the
main makefile.
The
David Fetter wrote:
On Tue, Jul 12, 2005 at 10:48:40AM -0400, Bruce Momjian wrote:
Peter Eisentraut wrote:
Am Dienstag, 12. Juli 2005 05:29 schrieb Bruce Momjian:
Bruce Momjian wrote:
The current state allows users to manually set the format, or
actually only one aspect of the
43 matches
Mail list logo
