Hi.
itagaki.takah...@oss.ntt.co.jp wrote:
(It would be a rare case, but) A large object might be referenced
by two or more rows because LO interface is split into two steps;
allocating oid and storing data for it. The oid could be stored in
two or more places and auto deletion would break
Tom Lane wrote:
Well, if they're all in your search_path then plain old \df will do
fine. If they're not in your search path then I think it gets pretty
questionable whether they're user defined in a real sense. It seems
more likely that you've got a pile of modules loaded, and which of
brilliant i'll give it a go... Now to sort out java :)
James Pye wrote:
On Apr 7, 2009, at 12:54 PM, John Lister wrote:
Cheers, nice to know it is possible... Now to see if i can get
java/python to do the same :) or to use a modified libpq somehow...
http://python.projects.postgresql.org
Tom Lane wrote:
Hiroshi Saito z-sa...@guitar.ocn.ne.jp writes:
I want to solve one problem before the release of 8.4.
However, since it also seems to be the new feature,
if not enough for 8.4, you may suggest that it is 8.5.
I'm not too clear on what this is really supposed to accomplish,
Magnus Hagander wrote:
Tom Lane wrote:
Magnus Hagander mag...@hagander.net writes:
Tom Lane wrote:
What makes more sense to me is to add a table to encnames.c that
provides the gettext name of every encoding that we support.
Do you mean a separate table there, or should we add a new column
On Tue, Apr 07, 2009 at 12:51:21PM -0400, Tom Lane wrote:
Sam Mason s...@samason.me.uk writes:
SELECT 'NaN'::float8;
SELECT ' NaN'::float8;
SELECT 'NaN '::float8;
SELECT '+NaN'::float8;
SELECT '-NaN'::float8;
Well, the +- part must be an artifact of your strtod()
Peter Eisentraut wrote:
On Tuesday 07 April 2009 13:09:42 Heikki Linnakangas wrote:
Patch attached. Instead of checking for LC_CTYPE == C, I'm checking
pg_get_encoding_from_locale(NULL) == encoding which is more close to
what we actually want. The downside is that
Log Message:
---
Tell gettext which codeset to use by calling bind_textdomain_codeset(). We
already did that on Windows, but it's needed on other platforms too when
LC_CTYPE=C. With other locales, we enforce (or trust) that the codeset of
the locale matches the server encoding so we don't
Teodor Sigaev wrote:
May be call of pg_bind_textdomain_codeset(textdomain(NULL)); should be
wrapped by ENABLE_NLS?
Yep, fixed. Thanks.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Wed, Apr 8, 2009 at 1:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 7, 2009 at 10:42 PM, Josh Berkus j...@agliodbs.com wrote:
So has fadvise been completely dropped from 8.4, or only partially?
Bitmap scans will support it, but index scans
I'll see if I can get an updated build pushed out sometime today.
I finally got around to trying this out using the March 24th build,
and it has the same issue...
Kev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Hi.
- Original Message -
From: Hiroshi Inoue in...@tpf.co.jp
Tom Lane wrote:
Hiroshi Saito z-sa...@guitar.ocn.ne.jp writes:
I want to solve one problem before the release of 8.4.
However, since it also seems to be the new feature,
if not enough for 8.4, you may suggest that it is
On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field kevinjamesfi...@gmail.com wrote:
I'll see if I can get an updated build pushed out sometime today.
I finally got around to trying this out using the March 24th build,
and it has the same issue...
I just installed it here on a clean VM and I see the
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 8, 2009 at 1:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
And please note that we think bitmap scans are the larger part of
the win anyway. What's left undone there is some marginal mopup.
Can you elaborate on this? I'm fuzzy on why index
Following this up, is there any docs on the binary wire format for arrays?
Thanks
- Original Message -
From: John Lister
To: pgsql-hackers@postgresql.org
Sent: Tuesday, April 07, 2009 7:54 PM
Subject: [HACKERS] Array types
Hi, using v8.3.5 and a number of client libraries
Martin Pihlak wrote:
Tom Lane wrote:
Well, if they're all in your search_path then plain old \df will do
fine. If they're not in your search path then I think it gets pretty
questionable whether they're user defined in a real sense. It seems
more likely that you've got a pile of modules
John Lister wrote:
Following this up, is there any docs on the binary wire format for arrays?
None that I know of.
Check out the backend source: (array_recv() and array_send() functions)
http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/arrayfuncs.c?rev=1.154
Or, look at
On Apr 8, 10:32 am, dp...@pgadmin.org (Dave Page) wrote:
On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field kevinjamesfi...@gmail.com wrote:
I'll see if I can get an updated build pushed out sometime today.
I finally got around to trying this out using the March 24th build,
and it has the same
Andrew Chernow wrote:
John Lister wrote:
Following this up, is there any docs on the binary wire format for
arrays?
None that I know of.
Check out the backend source: (array_recv() and array_send() functions)
On Wed, Apr 8, 2009 at 10:48 AM, John Lister
john.lister...@kickstone.com wrote:
Following this up, is there any docs on the binary wire format for arrays?
Thanks
Does java wrap libpq? If so, your best bet is probably going to be to
go the libpqtypes route. If you want help doing that, you
Cheers for the pointers. Am i right in thinking that if i get an array of
arrays, the nested arrays are sent in wire format as well - it seems to be
from the docs.
Secondly, comments are a bit scarse in the code, but am i also right in
thinking that an array indexing can start at an arbitrary
No unfortunately not, it is a JDBC type 4 java which is entirely written in
java. I've patched (as pointed out in another list) the base version to
handle binary data (still a couple of issues that seem unfinished) which has
given me clues, but the patch only supports simple types. I'm looking
Merlin Moncure wrote:
On Wed, Apr 8, 2009 at 10:48 AM, John Lister
john.lister...@kickstone.com wrote:
Following this up, is there any docs on the binary wire format for arrays?
Thanks
Does java wrap libpq?
No. The JDBC driver is a Type 4 pure java driver. It implements the
On Wed, Apr 8, 2009 at 3:49 PM, Bruce Momjian br...@momjian.us wrote:
We already had a huge discussion over 'S' and I think we did as good as
we can. I think we risk overcomplicating the API by adding U, but we
can revisit this in 8.5 once we get more feedback from users.
I think we'll need
On Wed, Apr 8, 2009 at 3:47 PM, Kevin Field kevinjamesfi...@gmail.com wrote:
On Apr 8, 10:32 am, dp...@pgadmin.org (Dave Page) wrote:
On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field kevinjamesfi...@gmail.com
wrote:
I'll see if I can get an updated build pushed out sometime today.
I finally
John Lister john.lister...@kickstone.com writes:
Cheers for the pointers. Am i right in thinking that if i get an array of
arrays, the nested arrays are sent in wire format as well - it seems to be
from the docs.
Postgres doesn't have arrays of arrays. There are multi-dimensional
arrays,
On Wed, Apr 8, 2009 at 4:11 PM, John Lister
john.lister...@kickstone.com wrote:
Cheers for the pointers. Am i right in thinking that if i get an array of
arrays, the nested arrays are sent in wire format as well - it seems to be
from the docs.
No, you can't easily get an array of arrays in
Greg Stark st...@enterprisedb.com writes:
On Wed, Apr 8, 2009 at 3:49 PM, Bruce Momjian br...@momjian.us wrote:
We already had a huge discussion over 'S' and I think we did as good as
we can. I think we risk overcomplicating the API by adding U, but we
can revisit this in 8.5 once we get more
On Wed, Apr 8, 2009 at 4:11 PM, John Lister
john.lister...@kickstone.com wrote:
Cheers for the pointers. Am i right in thinking that if i get an array of
arrays, the nested arrays are sent in wire format as well - it seems to
be
from the docs.
No, you can't easily get an array of arrays
Tom Lane escribió:
BTW, I hesitate to mention this and perhaps upset a fragile consensus,
but should we remove the special-case code in \df that tries to hide I/O
functions by excluding functions that take or return cstring? I think
that its value has largely disappeared given the new
On Wed, Apr 8, 2009 at 11:35 AM, Greg Stark st...@enterprisedb.com wrote:
On Wed, Apr 8, 2009 at 4:11 PM, John Lister
john.lister...@kickstone.com wrote:
Cheers for the pointers. Am i right in thinking that if i get an array of
arrays, the nested arrays are sent in wire format as well - it
On Wed, Apr 8, 2009 at 10:33 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 8, 2009 at 1:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
And please note that we think bitmap scans are the larger part of
the win anyway. What's left undone there is some
On Apr 8, 11:26 am, dp...@pgadmin.org (Dave Page) wrote:
Did you add
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
to postgresql.conf and restart the server per the README?
Oh my goodness. No. Thank you so much. It works fine now. I'll
have to add that to my upgrading
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 8, 2009 at 10:33 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The main point is that the planner will prefer a bitmap scan for any
query that's estimated to return more than quite a small number of rows.
That makes sense, but what about the
Alvaro Herrera wrote:
Tom Lane escribi?:
BTW, I hesitate to mention this and perhaps upset a fragile consensus,
but should we remove the special-case code in \df that tries to hide I/O
functions by excluding functions that take or return cstring? I think
that its value has largely
Hi Itagaki-san.
Um, I had a focus in help the problem which is not avoided.
I am not sensitive to a problem being avoided depending on usage.
However, I will wish to work spontaneously, when it is help much.
Regards,
Hiroshi Saito
- Original Message -
From: Itagaki Takahiro
On Wed, Apr 8, 2009 at 4:35 PM, Kevin Field kevinjamesfi...@gmail.com wrote:
On Apr 8, 11:26 am, dp...@pgadmin.org (Dave Page) wrote:
Did you add
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
to postgresql.conf and restart the server per the README?
Oh my goodness. No.
On Wed, Apr 8, 2009 at 11:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Apr 8, 2009 at 10:33 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The main point is that the planner will prefer a bitmap scan for any
query that's estimated to return more than
On 4/7/09 10:17 PM, Tom Lane wrote:
Robert Haasrobertmh...@gmail.com writes:
On Tue, Apr 7, 2009 at 10:42 PM, Josh Berkusj...@agliodbs.com wrote:
So has fadvise been completely dropped from 8.4, or only partially?
Bitmap scans will support it, but index scans will not.
What about seq
Josh Berkus j...@agliodbs.com writes:
What about seq scans?
If the kernel can't read-ahead a seqscan by itself, it's unlikely to
be smart enough to be helped by posix_fadvise ... or at least so I
would think. Do you have reason to think differently?
regards, tom lane
and...@tao11.riddles.org.uk (Andrew Gierth) writes:
The usual conversation goes something like this (generally following
on from some discussion of how to do timezone conversions):
Q: how do I get the list of available zone names?
A: see pg_timezone_names
Q: but there's
On 4/8/09 9:44 AM, Tom Lane wrote:
Josh Berkusj...@agliodbs.com writes:
What about seq scans?
If the kernel can't read-ahead a seqscan by itself, it's unlikely to
be smart enough to be helped by posix_fadvise ... or at least so I
would think. Do you have reason to think differently?
Well,
On Wednesday, April 8, 2009, Josh Berkus j...@agliodbs.com wrote:
On 4/8/09 9:44 AM, Tom Lane wrote:
Josh Berkusj...@agliodbs.com writes:
What about seq scans?
If the kernel can't read-ahead a seqscan by itself, it's unlikely to
be smart enough to be helped by posix_fadvise ... or at
Josh Berkus wrote:
On 4/8/09 9:44 AM, Tom Lane wrote:
Josh Berkusj...@agliodbs.com writes:
What about seq scans?
If the kernel can't read-ahead a seqscan by itself, it's unlikely to
be smart enough to be helped by posix_fadvise ... or at least so I
would think. Do you have reason to think
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
xlog.c now also uses POSIX_FADV_WONTNEED to drop WAL pages from the
OS cache after writing them.
Even when archiving is on?
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Dave Page wrote:
On Wednesday, April 8, 2009, Josh Berkus j...@agliodbs.com wrote:
Presumably fadvise is useless on Windows. Anyone know?
It is.
cygwin supports POSIX_FADV_SEQUENTIAL (and POSIX_FADV_NORMAL to revert
it), but not any of the other flags. It maps it to
Kevin Grittner wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
xlog.c now also uses POSIX_FADV_WONTNEED to drop WAL pages from the
OS cache after writing them.
Even when archiving is on?
No, not in that case.
--
Heikki Linnakangas
EnterpriseDB
Heikki Linnakangas wrote:
Dave Page wrote:
On Wednesday, April 8, 2009, Josh Berkus j...@agliodbs.com wrote:
Presumably fadvise is useless on Windows. Anyone know?
It is.
cygwin supports POSIX_FADV_SEQUENTIAL (and POSIX_FADV_NORMAL to revert
it), but not any of the other flags. It maps
Heikki,
It's important to distinguish what kind of fadvise we're talking about.
The bitmap scan code issues hints about individual pages, using
posix_fadvise(... POSIX_FADV_WILLNEED). For increasing the readahead of
a sequential scan, you'd want to use POSIX_FADV_SEQUENTIAL. I believe
the
Josh Berkus wrote:
The other thing I was going to ask you about is using posix_fadvise as
an alternative to O_DIRECT for the xlog. O_DIRECT is, AFAIK,
linux-only, whereas there are direct write fadvise flags which work on
multiple OSes.
What flags are those? I don't see any posix_fadvise
Magnus Hagander mag...@hagander.net writes:
Heikki Linnakangas wrote:
cygwin supports POSIX_FADV_SEQUENTIAL (and POSIX_FADV_NORMAL to revert
it), but not any of the other flags. It maps it to
NtSetInformationFile() like this:
We set this in our open() wrapper in the code today.
Really?
Tom Lane wrote:
Magnus Hagander mag...@hagander.net writes:
Heikki Linnakangas wrote:
cygwin supports POSIX_FADV_SEQUENTIAL (and POSIX_FADV_NORMAL to revert
it), but not any of the other flags. It maps it to
NtSetInformationFile() like this:
We set this in our open() wrapper in the code
On Wed, Apr 8, 2009 at 6:42 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Dave Page wrote:
On Wednesday, April 8, 2009, Josh Berkus j...@agliodbs.com wrote:
Presumably fadvise is useless on Windows. Anyone know?
It is.
cygwin supports POSIX_FADV_SEQUENTIAL (and
Tom,
change cardinality() for multi-dim arrays?
Drop; there's no consensus that this should be changed
Andrew pinged me on this. While there's no consensus that it should be
changed, there's no consensus it shouldn't, either. And once we release
it, we've set the way it operates
On Wed, 8 Apr 2009, Heikki Linnakangas wrote:
Josh Berkus wrote:
The other thing I was going to ask you about is using posix_fadvise as an
alternative to O_DIRECT for the xlog. O_DIRECT is, AFAIK, linux-only,
whereas there are direct write fadvise flags which work on multiple OSes.
What
On Wed, 8 Apr 2009, Tom Lane wrote:
If the kernel can't read-ahead a seqscan by itself, it's unlikely to
be smart enough to be helped by posix_fadvise ... or at least so I
would think.
There's some interesting comments on this subject (and about what fadvise
DONTNEED does) in the RRD
Josh Berkus j...@agliodbs.com writes:
Tom,
change cardinality() for multi-dim arrays?
Drop; there's no consensus that this should be changed
Andrew pinged me on this. While there's no consensus that it should be
changed, there's no consensus it shouldn't, either. And once we release
Tom,
There is no equivalent of multi-dimensional arrays in other kinds of
collections, so I'm not seeing that there is any good guide there.
What else *does* SQL:2008 consider a collection?
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list
Hi,
Following the discussion here
http://archives.postgresql.org/message-id/49d9e986.8010...@pse-consulting.de
, I wrote a small patch which rotates the last XLog file on shutdown
so that the archive command is also executed for this file and we are
sure we have all the useful XLog files when we
Hi,
Some one knows where can I download a full example of a variable length
user defined type? I'm trying to define one but I have problems with de
output function.
Thanks
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Wed, Apr 8, 2009 at 3:49 PM, kverdecia kverde...@uci.cu wrote:
Hi,
Some one knows where can I download a full example of a variable length
user defined type? I'm trying to define one but I have problems with de
output function.
have you looked at contrib? for example hstore?
merlin
--
kverdecia kverde...@uci.cu writes:
Some one knows where can I download a full example of a variable length
user defined type?
There are several in the contrib modules.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Friday 27 March 2009 20:59:23 Tom Lane wrote:
Done, but I noticed while testing that it's not real consistent:
regression=# select xmlelement(name foo, 'infinity'::timestamp);
ERROR: timestamp out of range
DETAIL: XML does not support infinite timestamp values.
regression=# select
How that debug_print_parse outputs as LOG instead of DEBUG in 8.4,
should it be log_print_parse?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sam Mason s...@samason.me.uk writes:
On Tue, Apr 07, 2009 at 12:51:21PM -0400, Tom Lane wrote:
IIRC, the explicit support for leading/trailing spaces is something that
we added in float8in long after numeric_in was written, and I think just
nobody thought about numeric at the time. But it's
Bruce Momjian br...@momjian.us writes:
Alvaro Herrera wrote:
Tom Lane escribi?:
BTW, I hesitate to mention this and perhaps upset a fragile consensus,
but should we remove the special-case code in \df that tries to hide I/O
functions by excluding functions that take or return cstring? I
Bruce Momjian br...@momjian.us writes:
How that debug_print_parse outputs as LOG instead of DEBUG in 8.4,
should it be log_print_parse?
No, it's still a debugging tool.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Wednesday 08 April 2009 21:56:38 Tom Lane wrote:
For my part, I'd like to know what things other than arrays
collection_expression in the standard applies to. I think the most
sensible course is to make cardinality(array[]) behave consistently with
cardinality(other_stuff) when we get
Peter Eisentraut pete...@gmx.net writes:
Here is my thinking, and considering that that would basically involve a
forward-looking design decision right now, I would support dropping the
cardinality() function from 8.4 (if people agree that this is in fact the
design decision to make).
At
On Tuesday 07 April 2009 03:36:43 Tom Lane wrote:
You won't get far with doing it to pg_proc: internal functions *have to*
have entries in there, else the fmgrtab infrastructure for them doesn't
get created. (Yeah, I suppose there are other ways to drive that, but
the fact remains that they
Peter Eisentraut pete...@gmx.net writes:
What is the purpose of fmgrtab anyway?
It's so we can find the addresses of internal functions to call them.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Tom,
Like what? I do not actually believe that anyone needs an
interactive geographical timezone selector based on
pg_timezone_names.
Actually, considering that PostgreSQL is the leading open source GIS
database, I expect that a *lot* of people want this. Or, at least,
enough data to
On Thursday 02 April 2009 21:38:06 Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Now, what about the idea of providing a shorthand LOCALE='foo',
mirroring --locale=foo initdb option? It seems like a good idea, because
you almost never want to set LC_COLLATE
Hiroshi Saito z-sa...@guitar.ocn.ne.jp wrote:
Um, I had a focus in help the problem which is not avoided.
I am not sensitive to a problem being avoided depending on usage.
However, I will wish to work spontaneously, when it is help much.
I'll research whether encoding of filesystem path
On Wed, Apr 08, 2009 at 06:11:59PM -0400, Tom Lane wrote:
Sam Mason s...@samason.me.uk writes:
On Tue, Apr 07, 2009 at 12:51:21PM -0400, Tom Lane wrote:
IIRC, the explicit support for leading/trailing spaces is something that
we added in float8in long after numeric_in was written, and I
Sam Mason s...@samason.me.uk writes:
On Wed, Apr 08, 2009 at 06:11:59PM -0400, Tom Lane wrote:
Anyway, I revised this a bit and applied to HEAD.
I've not tested; but your changes look as though they will break:
SELECT 'Infinity'::float::numeric;
That gives an error now, just as it did
On Thursday 09 April 2009 02:24:53 Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
What is the purpose of fmgrtab anyway?
It's so we can find the addresses of internal functions to call them.
Ah yes of course. But then the table can just as well be built by something
based on
Hi,
On Thu, Apr 9, 2009 at 4:11 AM, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi,
Following the discussion here
http://archives.postgresql.org/message-id/49d9e986.8010...@pse-consulting.de
, I wrote a small patch which rotates the last XLog file on shutdown
so that the archive command
78 matches
Mail list logo
