Tom Lane wrote:
alexander lunyov [EMAIL PROTECTED] writes:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket.
It won't work anyway: modern versions of pg_dump are only designed to
work with servers back to 7.0. I see from the
2008/8/17 Hannu Krosing [EMAIL PROTECTED]:
On Sun, 2008-08-17 at 17:59 +0200, Pavel Stehule wrote:
Hannu
it's not possible in plpgsql, because we are not able iterate via record.
just add function for iterating over record :)
it's not easy, when iterating should be fast - when record's
Am Sunday, 17. August 2008 schrieb Oleg Bartunov:
is there psql static binary, which I can use on my iphone (version 1) ?
I have no idea, but just as a thought, using phpPgAdmin might be a good
workaround.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Am Saturday, 16. August 2008 schrieb Hannu Krosing:
A label is the same thing as variable/attribute/argument name in
all programming languages I can think of. Why do you need two kinds of
argument names in postgreSQL ?
maybe you are after something like keyword arguments in python ?
Peter Eisentraut wrote:
Am Sunday, 17. August 2008 schrieb Oleg Bartunov:
is there psql static binary, which I can use on my iphone (version 1) ?
I have no idea, but just as a thought, using phpPgAdmin might be a good
workaround.
postgres seems to compile nicely on the iphone.
On Fri, 2008-08-15 at 14:25 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
Implementation would be to make PQreset() try secondary connection if
the primary one fails to reset. Of course you can program this manually,
but the feature is that you wouldn't need to, nor would you need
Hello
I did some fast test on pagila database.
8.4
postgres=# explain analyze select * from film f where exists (select
film_id from film_actor where f.film_id = film_id);
QUERY PLAN
2008/8/18 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
Le lundi 18 août 2008, Andrew Dunstan a écrit :
On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
This is not the kind of patch we put into stable branches.
So what? That is not the only criterion for backpatching.
I fail to
[EMAIL PROTECTED] 写道:
I wish to set up the Postgres-R environment, could you please let me know the
steps for setting it up.
Thanks.
yeah, actually, i have not been successful to set up this, but let me
give some information for you.
1. download the postgresql snapshot source code from
I haven't looked at it but there's this:
http://www.postgresql.org/about/news.988
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-hackers mailing list
On Mon, 2008-08-18 at 08:53 +0200, Pavel Stehule wrote:
2008/8/17 Hannu Krosing [EMAIL PROTECTED]:
On Sun, 2008-08-17 at 17:59 +0200, Pavel Stehule wrote:
Hannu
it's not possible in plpgsql, because we are not able iterate via record.
just add function for iterating over record :)
On Mon, 2008-08-18 at 10:51 +0300, Peter Eisentraut wrote:
Am Saturday, 16. August 2008 schrieb Hannu Krosing:
A label is the same thing as variable/attribute/argument name in
all programming languages I can think of. Why do you need two kinds of
argument names in postgreSQL ?
maybe
What I'm interested in is auto-tuning, not necessarily overhauling GUCS,
which happens to be the subject of this thread :-)
Having done a SELECT * FROM pg_settings, all the information you need seems
to be there...
Maybe I'm being over-simplistic here, but the important bit is knowing how
you
Tom Lane wrote:
A further suggestion is that you use -d or even -D option on the dump.
I think there have been some corner-case changes in COPY data format
since 6.5 days; which might or might not bite you, but why take the
chance ...
%/usr/local/pgsql/bin/pg_dump -D itt_user itt_user.dump
I have been hacking around for a while trying to create some example Oracle
compatibility types. Canonical examples: varchar2 and number. With the new
features in 8.3 and 8.4, such as user-definable typmods and type categories,
it appears to be actually possible to create a type equivalent to
Am Friday, 15. August 2008 schrieb Tom Lane:
well, contrib/xml2/xslt_proc.c has 172 lines. So I suggest we just
import that to core and drop the rest of the module as redundant.
I assume that wouldn't provide the functionality Peter wants; else the
above would have happened already in 8.3.
On Mon, 18 Aug 2008, Gregory Stark wrote:
I haven't looked at it but there's this:
http://www.postgresql.org/about/news.988
Yes, I know it. But, it's not free and one should use iTunes program
to buy it from AppStore.
Regards,
Oleg
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
There is also another possible way one might want to create a compatibility
type. Instead of creating a new type, create an alias for an existing type,
much like we currently have built-in mappings for int - int4, bigint -
int8, etc. The
In my experience synonyms as well as rules are hacks and should be avoided
althou there are cases where they can save some work for dba's during
transitions from one situation to better one.
There is also another possible way one might want to create a
compatibility
type. Instead of creating a
On Mon, Aug 18, 2008 at 4:02 AM, Hans-Juergen Schoenig
[EMAIL PROTECTED] wrote:
Peter Eisentraut wrote:
Am Sunday, 17. August 2008 schrieb Oleg Bartunov:
is there psql static binary, which I can use on my iphone (version 1) ?
I have no idea, but just as a thought, using phpPgAdmin might
postgres seems to compile nicely on the iphone.
compilations stops at gram.c however :) the file is just too big to compile
on 96MB of RAM :).
first the screen turns to black and then it reboots.
so far i have not seen how i can add a swap file to the iphone and i was too
lazy to cross compile
On Mon, Aug 18, 2008 at 9:16 AM, Hans-Juergen Schoenig [EMAIL PROTECTED]
compilations stops at gram.c however :) the file is just too big to
compile
on 96MB of RAM :).
first the screen turns to black and then it reboots.
so far i have not seen how i can add a swap file to the iphone and i
Thanks for the information.
For Step5 (starting ensemble daemon).-
I set the multicast address to both nodes (Node 1 Node 2 eth0: 224.0.0.9/4)
before starting the ensemble. And started the server application mtalk in node
1 node 2 and then client application in node 1 node 2. But the count
Peter Eisentraut [EMAIL PROTECTED] writes:
So while thinking about how to make this simpler I remembered the distinct
type feature of SQL, which works quite similarly, namely the new type has
the same structure as the old type, but is a separate entity. It looks like
CREATE TYPE newtype
Tom Lane wrote:
Thanks, and while I approve of that TODO, that's not actually the one I
was talking about in the email. The one I was talking about was change
builtin set-returning functions to use OUT parameters so you can query
them without knowing the result format or something like
On Aug 18, 2008, at 1:05 AM, Magnus Hagander wrote:
Josh Berkus wrote:
Steve,
First pass is done. Needs a little cleanup before sharing. I spent a
fair while down OS-specific-hardware-queries rathole, but I'm
better now.
Gods, I hope you gave up on that. You want to use SIGAR or
Steve Atkins wrote:
On Aug 18, 2008, at 1:05 AM, Magnus Hagander wrote:
Josh Berkus wrote:
Steve,
First pass is done. Needs a little cleanup before sharing. I spent a
fair while down OS-specific-hardware-queries rathole, but I'm better
now.
Gods, I hope you gave up on that. You want
Is this a TODO?
---
Hannu Krosing wrote:
On Mon, 2008-08-18 at 08:53 +0200, Pavel Stehule wrote:
2008/8/17 Hannu Krosing [EMAIL PROTECTED]:
On Sun, 2008-08-17 at 17:59 +0200, Pavel Stehule wrote:
Hannu
it's
On Mon, 2008-08-18 at 11:19 -0400, Bruce Momjian wrote:
Is this a TODO?
I don't think we have a TODO yet.
Maybe a TBD :)
---
Hannu Krosing wrote:
On Mon, 2008-08-18 at 08:53 +0200, Pavel Stehule wrote:
2008/8/17
There may be a TODO in this thread somewhere, but I think this
particular suggestion has drifted pretty far from the problem that
Pavel was trying to solve.
...Robert
On Mon, Aug 18, 2008 at 11:19 AM, Bruce Momjian [EMAIL PROTECTED] wrote:
Is this a TODO?
it's not possible in plpgsql,
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
On Tue, 2008-08-12 at 15:46 -0400, Tom Lane wrote:
This is only going to matter for a table of 1 block (or at least very
few blocks), and for such a table it's highly likely that it's in RAM
anyway. So I'm
On Mon, 2008-08-18 at 16:44 +0100, Gregory Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
On Tue, 2008-08-12 at 15:46 -0400, Tom Lane wrote:
This is only going to matter for a table of 1 block (or at least
very
few blocks), and for such a table
alexander lunyov [EMAIL PROTECTED] writes:
Tom Lane wrote:
I wonder if you need these self defined aggregates at all, most or all
of them are in 8.3 already.
They aren't self defined in 6.5 either.
So i can't just delete those AGGREGATEs?
I think what is happening
is that he's trying
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
I'm not necessarily opposed to making this change --- it does sound
kinda plausible --- but I want to see some hard evidence that it does
more good than harm before we put it in.
I don't want to see this thread
On Monday 18 August 2008 03:47:06 Peter Eisentraut wrote:
Am Sunday, 17. August 2008 schrieb Oleg Bartunov:
is there psql static binary, which I can use on my iphone (version 1) ?
I have no idea, but just as a thought, using phpPgAdmin might be a good
workaround.
I've played with this a
On Mon, 18 Aug 2008, Michael Nacos wrote:
Having done a SELECT * FROM pg_settings, all the information you need
seems to be there...
See http://archives.postgresql.org/pgsql-hackers/2008-06/msg00209.php You
sound like you're at rung 2 on the tool author ladder I describe there,
still
On Monday 18 August 2008 17:26:16 Tom Lane wrote:
This feature by itself could be quite useful, and then we could simply
add something like
CREATE TYPE newtype AS oldtype WITH CASTS;
This seems like a great way to get lost in ambiguous function hell ...
I don't understand this point.
Greg Smith [EMAIL PROTECTED] writes:
On Tue, 12 Aug 2008, Tom Lane wrote:
This seems like a fairly bad idea, because it introduces a
gettimeofday() call per transaction.
There's already lots of paths through pgbench that introduce gettimeofday
calls all over the place. I fail to see how
Howdy,
A while back, thanks to feedback from RhodiumToad on #postgresql, I
added selectivity functions to the citext operators:
CREATE OPERATOR = (
LEFTARG= CITEXT,
RIGHTARG = CITEXT,
COMMUTATOR = =,
NEGATOR= ,
PROCEDURE = citext_eq,
RESTRICT = eqsel,
Peter Eisentraut [EMAIL PROTECTED] writes:
On Monday 18 August 2008 17:26:16 Tom Lane wrote:
This feature by itself could be quite useful, and then we could simply
add something like
CREATE TYPE newtype AS oldtype WITH CASTS;
This seems like a great way to get lost in ambiguous function
Greg Smith [EMAIL PROTECTED] writes:
On Mon, 18 Aug 2008, Michael Nacos wrote:
Having done a SELECT * FROM pg_settings, all the information you need seems
to be there...
See http://archives.postgresql.org/pgsql-hackers/2008-06/msg00209.php You
sound
like you're at rung 2 on the tool
David E. Wheeler [EMAIL PROTECTED] writes:
From what depesz sees, the eqsel and eqjoinsel functions might be a
bit too aggressive in recommending the use of indexes.
He presented absolutely 0 evidence to back up that opinion.
So I was wondering, since in CVS HEAD citext is able to identify
Greg,
The entire target market for such a thing is DBAs stuck on hosted
databases which don't have shell access to their machines.
That's incorrect. The main reason for having a port-based API (such as the
SQL command line) for managing your server is that it makes it much easier
to manage
Gregory Stark [EMAIL PROTECTED] writes:
The entire target market for such a thing is DBAs stuck on hosted databases
which don't have shell access to their machines. Perhaps the overlap between
that and the people who can write a server-side module which dumps out a
config file according to
On Aug 18, 2008, at 12:18, Tom Lane wrote:
David E. Wheeler [EMAIL PROTECTED] writes:
From what depesz sees, the eqsel and eqjoinsel functions might be a
bit too aggressive in recommending the use of indexes.
He presented absolutely 0 evidence to back up that opinion.
So I was wondering,
On Sun, Aug 17, 2008 at 4:29 PM, in message
[EMAIL PROTECTED],
Tom Lane [EMAIL PROTECTED] wrote:
If you're still interested in testing CVS HEAD's handling of EXISTS,
I've about finished what I wanted to do with it.
Thanks. I'm very interested; unfortunately I can't get to it until at
least
Josh Berkus [EMAIL PROTECTED] writes:
Greg,
The entire target market for such a thing is DBAs stuck on hosted
databases which don't have shell access to their machines.
That's incorrect. The main reason for having a port-based API (such as the
SQL command line) for managing your server
Greg,
The main problem that I've seen described is what I mentioned before:
allowing adjusting the postgresql.conf GUC settings by remote users who
don't have shell access.
Oh, ok. I think we're in agreement, though. I don't think that's the
*1st* problem to be solved, but it's definitely
On Mon, Aug 18, 2008 at 8:51 PM, Gregory Stark [EMAIL PROTECTED] wrote:
The main problem that I've seen described is what I mentioned before: allowing
adjusting the postgresql.conf GUC settings by remote users who don't have
shell access.
Which pgAdmin has done perfectly well for years, as
Folks,
As the things stored in databases grow, we're going to start needing
to think about database objects that 4 bytes of size can't describe.
People are already storing video in lo and bytea fields. To date, the
sizes of media files have never trended downward.
What would need to happen for
On Mon, 18 Aug 2008, Gregory Stark wrote:
Because coping with free-form user-edited text is a losing game. People
don't consider it because it's a dead-end.
Right, that's impossible technology to build, which is why I had to plan
all these screen shots showing tools that handle that easily
David Fetter [EMAIL PROTECTED] writes:
What would need to happen for the next jump up from where varlena is
now, to 8 bytes?
Dealing with upwards-of-4GB blobs as single Datums isn't remotely sane,
and won't become so in the near (or even medium) future. So I don't
see the point of doing all
On Mon, 18 Aug 2008, Tom Lane wrote:
the seldom-used log-each-transaction option, which pretty obviously
is a drag on performance anyway
I always recommend that people run with log each transaction turned on,
beause it's the only way to gather useful latency information. I think
runs that
On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
2008/8/18 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
Le lundi 18 août 2008, Andrew Dunstan a écrit :
On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
This is not the kind of patch we put into stable branches.
So what?
Dave Page wrote:
On Mon, Aug 18, 2008 at 8:51 PM, Gregory Stark [EMAIL PROTECTED] wrote:
The main problem that I've seen described is what I mentioned before:
allowing
adjusting the postgresql.conf GUC settings by remote users who don't have
shell access.
Which pgAdmin has done perfectly
2008/8/18 Hannu Krosing [EMAIL PROTECTED]:
On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
2008/8/18 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
Le lundi 18 août 2008, Andrew Dunstan a écrit :
On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
This is not the kind of patch
Does it change of result some queries?
Patch in itself is not changing what the queries return. It just gets rid of
error condition from which Postgres itself is not able to recover.
It is protection to server's hang?
For users of stored procedures it is protection from downtime. For Skype it
On Mon, Aug 18, 2008 at 04:22:56PM -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
What would need to happen for the next jump up from where varlena
is now, to 8 bytes?
Dealing with upwards-of-4GB blobs as single Datums isn't remotely
sane, and won't become so in the near
On 8/18/08, Magnus Hagander [EMAIL PROTECTED] wrote:
Dave Page wrote:
On Mon, Aug 18, 2008 at 8:51 PM, Gregory Stark [EMAIL PROTECTED]
wrote:
The main problem that I've seen described is what I mentioned before:
allowing
adjusting the postgresql.conf GUC settings by remote users who don't
Tom Lane escribió:
Gregory Stark [EMAIL PROTECTED] writes:
The entire target market for such a thing is DBAs stuck on hosted databases
which don't have shell access to their machines. Perhaps the overlap between
that and the people who can write a server-side module which dumps out a
The second annual PostgreSQL Conference: West is being held on October
10th through October 12th 2008 in the The Native American Student
Community Center at Portland State University.
We are currently accepting papers and you can submit your talks here:
David Fetter wrote:
Folks,
As the things stored in databases grow, we're going to start needing
to think about database objects that 4 bytes of size can't describe.
People are already storing video in lo and bytea fields. To date, the
sizes of media files have never trended downward.
I
Greg Smith wrote:
On Mon, 18 Aug 2008, Tom Lane wrote:
I repeat my concern that transaction rates measured with this patch will
be significantly different from those seen with the old code
Last time I tried to quantify the overhead of logging with timestamps on
I couldn't even measure its
On Mon, Aug 18, 2008 at 06:09:13PM -0400, Andrew Chernow wrote:
David Fetter wrote:
Folks,
As the things stored in databases grow, we're going to start
needing to think about database objects that 4 bytes of size can't
describe. People are already storing video in lo and bytea fields.
To
David Fetter wrote:
On Mon, Aug 18, 2008 at 06:09:13PM -0400, Andrew Chernow wrote:
David Fetter wrote:
Folks,
As the things stored in databases grow, we're going to start
needing to think about database objects that 4 bytes of size can't
describe. People are already storing video in lo and
Andrew,
I always find these requests puzzling. Is it really useful to store the
data for a jpeg, video file or a 10GB tar ball in a database column?
Some people find it useful. Because LOs are actually easier to manage in
PG than in most other DBMSes, right now that's a significant source
I always find these requests puzzling. Is it really useful to store the
data for a jpeg, video file or a 10GB tar ball in a database column?
One use case is that it can use the existing postgresql protocol, and
does not require extra filesystem mounts, extra error handling, and
other
Andrew Chernow [EMAIL PROTECTED] writes:
Anyways (back on topic), I am in favor of removing limits from any
section of the database ... not just your suggestion. The end-user
application should impose limits.
That's nice as an abstract principle, but there are only so many hours
in the day,
Tom Lane wrote:
Andrew Chernow [EMAIL PROTECTED] writes:
Anyways (back on topic), I am in favor of removing limits from any
section of the database ... not just your suggestion. The end-user
application should impose limits.
That's nice as an abstract principle, but there are only so many
Jeff Davis wrote:
I always find these requests puzzling. Is it really useful to store the
data for a jpeg, video file or a 10GB tar ball in a database column?
One use case is that it can use the existing postgresql protocol,
So can what I am suggesting. How about a user-defined C
David Fetter [EMAIL PROTECTED] writes:
On Mon, Aug 18, 2008 at 04:22:56PM -0400, Tom Lane wrote:
The main things I think we'd need to consider besides just the
access API are
- permissions features (more than none anyway)
Would ROLEs work, or are you thinking of the per-row and per-column
David Fetter [EMAIL PROTECTED] writes:
On Mon, Aug 18, 2008 at 06:09:13PM -0400, Andrew Chernow wrote:
I always find these requests puzzling. Is it really useful to store
the data for a jpeg, video file or a 10GB tar ball in a database
column?
It is if you need transaction semantics.
Alvaro Herrera [EMAIL PROTECTED] writes:
Greg Smith wrote:
Last time I tried to quantify the overhead of logging with timestamps on
I couldn't even measure its impact, it was lower than the usual pgbench
noise.
There's a hardware deficiency on certain machines -- I think it's old
ones.
Asko Oja [EMAIL PROTECTED] writes:
For users of stored procedures it is protection from downtime. For Skype it
has been around 20% of databse related downtime this year.
Perhaps Skype needs to rethink how they are modifying functions.
The reason that this case wasn't covered in 8.3 is that
On Mon, Aug 18, 2008 at 07:31:04PM -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
On Mon, Aug 18, 2008 at 04:22:56PM -0400, Tom Lane wrote:
The main things I think we'd need to consider besides just the
access API are
- permissions features (more than none anyway)
David Fetter wrote
...
This'd greatly simplify the
cleanup-dead-objects problem, and we could avoid addressing the
permissions problem at all, since regular SQL permissions on the table
would serve fine. But it's not clear what regular SQL fetch and update
behaviors should be like
hi,
Assume that we have two node
node 0 , 192.168.0.2
node 1 , 192.168.0.3
1. add a host entry in /etc/hosts for hostname resolving.
2. add the host list in configuration 'ensemble.conf' for gossip service:
ENS_GOSSIP_HOSTS=node0:node1
3. set the envrionment variable ENS_CONFIG_FILE
export
The examples that Kevin Grittner put up awhile back included several
uses of EXISTS() in places where it couldn't be turned into a semijoin,
eg in the query's targetlist. I was musing a bit about whether we could
improve those scenarios. I would like to get 8.4 to the point where we
could say as
Tom Lane [EMAIL PROTECTED] wrote:
My understanding is that it's basically cheap PC hardware (with clock
interfaces based on old ISA bus specs) that has the issue in a
significant way. I wouldn't expect you to see it on a serious database
server. But lots of people still do development on
ITAGAKI Takahiro wrote:
The only thing I worried about is portability issue. POSIX functions
like alarm() or setitimer() are not available at least on Windows.
I expect alarm() is available on all platforms except Win32 and
used CreateTimerQueue() instead on Win32 in the new patch.
(We have
Tom Lane wrote:
I don't think any of this is out of reach, but it'd be a nontrivial
bit of implementation effort (maybe a week or three) and it also looks
like there might be a measurable planning slowdown for any query
involving subqueries. I'm not sure yet how much of this is just moving
For various reasons others have not been able to discuss detailed
designs in public. In an attempt to provide assistance with that I'm
providing my design notes here - not hugely detailed, just rough
sketches of how it can work. This may also help identify coordination
points and help to avert the
On Mon, 2008-08-18 at 16:22 -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
What would need to happen for the next jump up from where varlena is
now, to 8 bytes?
Dealing with upwards-of-4GB blobs as single Datums isn't remotely sane,
and won't become so in the near (or even
Simon Riggs [EMAIL PROTECTED] writes:
Probably also using a separate Sequence to allocate numbers rather than
using up all the Oids on LOs would be a good plan.
Well, assuming that your Large Objects are actually Large, you aren't
going to need as many OIDs as all that ;-)
However: I was
On Mon, 2008-08-18 at 23:43 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Probably also using a separate Sequence to allocate numbers rather than
using up all the Oids on LOs would be a good plan.
Well, assuming that your Large Objects are actually Large, you aren't
going
I would like to make a simple change to Resource Manager code to
introduce a plugin that can redefine or extend Rmgrs.
Providing an rmgr plugin in this way will also allow:
* filtering/control over apply of certain WAL records. We might decide
to skip all but certain tables, indexes, tablespaces
Hello,
Postgres supports to add custom GUC variables on runtime, but we
cannot use GUC flags in them. This patch adds the flags argument
to DefineCusomXxx() functions. The flags were always 0 until now.
GUC flags are useful for variables with units. Users will be able
to add configuration
On Mon, Aug 18, 2008 at 04:38:52PM +0900, Tatsuo Ishii wrote:
Hi,
Here is the latest WITH RECURSIVE patches against CVS HEAD. Besides
syncing to CVS HEAD, followings are main differences from previous
one:
Thanks for the new patch :)
I think I may have found another bug:
WITH RECURSIVE
88 matches
Mail list logo
