On Wed, Aug 4, 2010 at 3:11 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alex Hunsaker bada...@gmail.com writes:
On Wed, Aug 4, 2010 at 11:04, Tom Lane t...@sss.pgh.pa.us wrote:
If we were a bit earlier in the 9.0 cycle I would suggest that this
confusion is a sufficient reason to drop the
While chatting with Haas off-list regarding how the new array/string
functions should work (see the thread in its glory here:
http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg148865.html)
the debate morphed into the relative pros and cons about the proposed
concat() being marked stable
On Wed, Aug 4, 2010 at 5:09 PM, Nilson nilson.bra...@gmail.com wrote:
The prices of large capacity Solid State Disks (SLCs of course) are still
too high to most of us.
But it´s already possible to find SSDs of small size (8 to 32 GB) today with
affordable prices and good performance (0,1ms
On Wed, Aug 4, 2010 at 7:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
While chatting with Haas off-list regarding how the new array/string
functions should work (see the thread in its glory here:
http://www.mail-archive.com/pgsql-hackers@postgresql.org
On Wed, Aug 4, 2010 at 9:31 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Aug 4, 2010 at 6:43 PM, Merlin Moncure mmonc...@gmail.com wrote:
*) also, isn't it possible to change text cast influencing GUCs 'n'
times per statement considering any query can call a function and any
function
On Thu, Aug 5, 2010 at 7:25 AM, Simon Riggs si...@2ndquadrant.com wrote:
Also had these fragments as well, if they're still useful. Probably just
useful as pointers as to what else to change to include the docs.
The tests and docs were written from SQL standard, so any deviations
would need
On Thu, Aug 5, 2010 at 12:59 PM, Chris Browne cbbro...@acm.org wrote:
mmonc...@gmail.com (Merlin Moncure) writes:
On Wed, Aug 4, 2010 at 9:31 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Aug 4, 2010 at 6:43 PM, Merlin Moncure mmonc...@gmail.com wrote:
*) also, isn't it possible
Attached is a patch to remove the upsert example from the pl/pgsql
documentation. It has a serious bug (see:
http://www.spinics.net/lists/pgsql/msg112560.html) which is nontrivial
to fix. IMNSHO, our code examples should encourage good practices and
style.
The 'correct' way to do race free
On Thu, Aug 5, 2010 at 2:09 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
Attached is a patch to remove the upsert example from the pl/pgsql
documentation. It has a serious bug (see:
http://www.spinics.net/lists/pgsql/msg112560.html) which is nontrivial
On Mon, Aug 9, 2010 at 4:08 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Brendan Jurd dire...@gmail.com writes:
I have attached v4 of the patch against HEAD, and also an incremental
patch showing just my changes against v3.
I'll mark this as ready for committer.
Looking at this, I want to
On Mon, Aug 9, 2010 at 4:34 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
Is there any reason why array functions need the type prefix when
other type conversion functions don't? Why didn't we name unnest()
array_unnest()?
UNNEST() is in the standard, IIRC
On Thu, Sep 2, 2010 at 7:17 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from John Adams's message of jue sep 02 18:25:45 -0400 2010:
I noticed in postgres you cannot return multiple result sets from a stored
procedure (surprisingly as it looks like a very good dbms).
If
On Fri, Sep 3, 2010 at 4:07 PM, Josh Berkus j...@agliodbs.com wrote:
I noticed in postgres you cannot return multiple result sets from a
stored procedure (surprisingly as it looks like a very good dbms).
That feature has been on the TODO list for years. However, nobody has
stepped forward
On Sat, Sep 4, 2010 at 10:10 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
Also as mentioned upthread there are effective workarounds if you poke
around a bit. This is a FAQ, and there are about 3-4 solid methods
(if you search the archives) that cover most problems you would be
looking at
On Sun, Sep 5, 2010 at 2:26 PM, Peter Eisentraut pete...@gmx.net wrote:
On fre, 2010-09-03 at 16:18 -0400, Tom Lane wrote:
Part of the reason it's sat on TODO is lack of consensus about how
such a feature ought to look/work; particularly since most of the
discussion about it has considered
In my gripe/suggestion here:
http://archives.postgresql.org/pgsql-hackers/2008-12/msg00642.php
I noted that it might be nice to handle check constraints over
composite types. It turns out that table check constraints are not
enforced during casts:
postgres=# create table foo(f1 int, f2 int,
On Mon, Mar 26, 2007 at 10:30 AM, Andrew Dunstan and...@dunslane.net wrote:
This feature (ability to add a message payload to a NOTIFY) is on the TODO
list and I had undertaken to implement it. However, pressure of other work
has conspired to make that difficult, and Abhijit Menon-Sen recently
On Sat, Jan 3, 2009 at 1:32 AM, Alex Hunsaker bada...@gmail.com wrote:
On Fri, Jan 2, 2009 at 18:46, Tom Lane t...@sss.pgh.pa.us wrote:
It would be fairly easy, I think, to add some reloption fields that
would let these parameters be controlled on a per-table level.
+1
Or something easier
On Mon, Jan 5, 2009 at 11:45 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Peter Eisentraut escribió:
James Mansion wrote:
Peter Eisentraut wrote:
c. Are there any well-known pitfalls/objections which would prevent
me from
changing the algorithm to something more efficient (read:
On 1/12/09, Guillaume Smet guillaume.s...@gmail.com wrote:
On Mon, Jan 12, 2009 at 3:04 PM, Tom Lane t...@sss.pgh.pa.us wrote:
However, we are getting off onto a tangent. I wasn't trying to start
a discussion about general project policies, but about the specific
status of this
On 1/12/09, Joshua D. Drake j...@commandprompt.com wrote:
Basically I think we are up against the same type of project management
decision we've had several times before: are we willing to slip the
8.4 release schedule for however long it will take for hot standby
and the other
On 1/14/09, Bruce Momjian br...@momjian.us wrote:
OK, patch attached and applied to CVS HEAD. The nsl (not 'nls') library
check was removed in Postgres 8.2 here:
As long as you are looking at this, can you take a peek at this patch?
On Thu, Jan 15, 2009 at 5:14 AM, Jasen Betts ja...@xnet.co.nz wrote:
On 2009-01-14, Gerhard Heift ml-postgresql-20081012-3...@gheift.de wrote:
Hello,
is it possible to call a trigger for a row in a table without updating the
row? I want to do it in plpgsql.
Something like UPDATE table WHERE
On 1/16/09, Magnus Hagander mag...@hagander.net wrote:
Andrew Chernow wrote:
WSACleanup is not really needed during a PQfinish. Its horribly slow if
the library ref count is 0 and it actually unloads the winsock library,
adds 225ms to PQfinish.
Option A will make us leak the
On 1/20/09, Peter Eisentraut pete...@gmx.net wrote:
integer[] is array of integer, in the way C deals with arrays. This is
also a main reason why composite types and arrays don't mix orthogonally;
there is no way to represent that in the system catalogs.
What do you mean by this exactly?
On 1/23/09, Alvaro Herrera alvhe...@commandprompt.com wrote:
Simon Riggs wrote:
On Fri, 2009-01-23 at 12:58 +0200, Devrim GÜNDÜZ wrote:
On Fri, 2009-01-23 at 10:05 +, Simon Riggs wrote:
I'll add it now, default = on.
Did you mean off?
No, do you?
Depends on the
On 1/23/09, Tom Lane t...@sss.pgh.pa.us wrote:
Right at the moment I'm wondering why we are going to change the code
now to support a ten-year-old OS version that evidently no one has tried
to use Postgres on before.
I'd like to address this observation. You may have noticed that eSilo
has
On 1/26/09, Tom Lane t...@sss.pgh.pa.us wrote:
Gregory Stark st...@enterprisedb.com writes:
Put another way, the choice here is whether to have a half-baked delayed
8.4
release in 6 months or a polished on-time 8.5 release in 12 months. Either
way
the feature ships and on a not
On 1/26/09, Jonah H. Harris jonah.har...@gmail.com wrote:
On Mon, Jan 26, 2009 at 11:11 AM, Merlin Moncure mmonc...@gmail.com wrote:
What about a compromise solution: release 8.4 now, then focus on
wrapping up the big ticket items that didn't make it into 8.4 into a
quick (as possible) 8.5
On 1/26/09, Josh Berkus j...@agliodbs.com wrote:
All,
So, some feedback to make this decision more difficult:
Users: care about HS more than anything else in the world. I'm convinced
that if we took a staw poll, 80% of our users would be in favor of waiting
for HS. This one feature will
On 1/26/09, Gregory Stark st...@enterprisedb.com wrote:
Merlin Moncure mmonc...@gmail.com writes:
HS is working very well (Simon's ongoing work aside). I am pretty
confident based on my personal testing that it would represent the
project well if committed today.
I think a lot
On 1/27/09, Zdenek Kotala zdenek.kot...@sun.com wrote:
This patch is mandatory for page online conversion and MUST TO be part
of postgreSQL 8.4. if not ... then we will be at the beginning next
year.
Just to clarify, does that mean that your patch has to be in for there
to be any chance of
IMO, composite types on insert/update should work as they do on select:
SELECT foo FROM foo; -- works, returning type foo
INSERT INTO foo VALUES '(something)'::foo -- fails,
but we have a workaround:
INSERT INTO foo SELECT ('(something)'::foo).* -- expands foo into foo columns
however no such
On 1/30/09, Sam Mason s...@samason.me.uk wrote:
On Wed, Jan 28, 2009 at 12:03:56PM -0500, Merlin Moncure wrote:
IMO, composite types on insert/update should work as they do on select:
The VALUES command is just a convenient way of getting lots of tuples
into PG isn't it? If the above
On 1/30/09, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
You are missing the point, using the composite type allows you to
build the insert without knowing the specific layout of the
table...
Surely at *some* level you have to know that.
You don't (if I
On 1/30/09, Sam Mason s...@samason.me.uk wrote:
quite often (i.e. a VALUES command with many singletons). This seems
a bit annoying and appears to be what you were suggesting you wanted
before (although you killed the relevant bit of context, making me think
we may be talking about
On 1/30/09, Sam Mason s...@samason.me.uk wrote:
On Fri, Jan 30, 2009 at 03:12:27PM -0500, Merlin Moncure wrote:
On 1/30/09, Sam Mason s...@samason.me.uk wrote:
quite often (i.e. a VALUES command with many singletons). This seems
a bit annoying and appears to be what you were
On 1/30/09, Sam Mason s...@samason.me.uk wrote:
But why not just leave INSERT as it is, it works and is unambiguous!
Because *there is no way to insert a composite type!!!* (you can
expand the type via INSERT ... SELECT, but not for UPDATE).
SELECT foo FROM foo; pulls the foo composite from the
On 1/30/09, Merlin Moncure mmonc...@gmail.com wrote:
likewise, with aliases
select foo f from foo; -- this is how it works now
update foo f set f=somefoo; -- again, this is how it should work
thinko:
select f from foo f; -- this is how it really works now
merlin
--
Sent via pgsql-hackers
On Wed, Feb 4, 2009 at 1:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Merlin Moncure mmonc...@gmail.com writes:
Noticed another issue with 'client only' type installs in the
Makefile. Shouldn't make install on libpq install postgres_ext.h in
addition to the interface
On Tue, Feb 10, 2009 at 9:32 AM, Magnus Hagander mag...@hagander.net wrote:
How we worked around it:
We solved it by copying the SSL init sequence from fe-secure.c. Doesn't
seem like something that would change very often. So we
init_our_library(), PQinitSSL(0) and then do a few lines of SSL
On Tue, Feb 10, 2009 at 11:52 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
Would someone remind me why turning off ssl initialization in libpq does
not work for this case?
That initializes both libcrypto and libssl. The problem arises when
libcrypto has been initialized
On Tue, Feb 10, 2009 at 11:14 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Well, you could create PQinitSSLExtended, but, as you say, the use
case is pretty narrow...
It would help if there were a PQgetLibraryVersion() function.
Help how? There is nothing
On Tue, Feb 10, 2009 at 11:54 AM, Bruce Momjian br...@momjian.us wrote:
Merlin Moncure wrote:
On Tue, Feb 10, 2009 at 11:52 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
Would someone remind me why turning off ssl initialization in libpq does
not work for this case
On Tue, Feb 10, 2009 at 12:03 PM, Dave Page dp...@pgadmin.org wrote:
On Tue, Feb 10, 2009 at 4:57 PM, Merlin Moncure mmonc...@gmail.com wrote:
PQinitSSL is *broken*. It's always been broken. Since it already
takes a parameter, I say add a special switch...the backwards
compatibility danger
On Tue, Feb 10, 2009 at 12:03 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Tue, Feb 10, 2009 at 11:54 AM, Bruce Momjian br...@momjian.us wrote:
Merlin Moncure wrote:
On Tue, Feb 10, 2009 at 11:52 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
Would someone remind me why
On Tue, Feb 10, 2009 at 1:02 PM, Magnus Hagander mag...@hagander.net wrote:
Merlin Moncure wrote:
On Tue, Feb 10, 2009 at 12:03 PM, Dave Page dp...@pgadmin.org wrote:
On Tue, Feb 10, 2009 at 4:57 PM, Merlin Moncure mmonc...@gmail.com wrote:
PQinitSSL is *broken*. It's always been broken
On Tue, Feb 10, 2009 at 5:02 PM, Bruce Momjian br...@momjian.us wrote:
Merlin Moncure wrote:
PQinitSSL(0) was specifically designed to allow applications to set up
SSL on their own. How does this not work properly?
this has nothing to do with who initializes ssl. this is all about
On Fri, Feb 13, 2009 at 3:06 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Chernow a...@esilo.com writes:
Maybe the argument to PQinitSSLExtended should be a bit mask, making
this version more extendable ... PG_INITSSL, PG_INITCRYPTO?
+1 for thinking ahead to the next time, but is a bit mask
On Fri, Feb 13, 2009 at 4:53 PM, Robert Haas robertmh...@gmail.com wrote:
BTW, the bitmask isn't perfect either --- doesn't it just reintroduce
the problem already complained of with your idea for PQinitSSL? That
is, how does the client know whether the function recognized all the
bits it
create table foo(a int, b int);
postgres=# create function rfoo() returns setof foo as $$ begin return
query select foo from foo; end; $$ language plpgsql;
CREATE FUNCTION
Time: 25.606 ms
postgres=#
postgres=#
postgres=# select rfoo();
ERROR: structure of query does not match function result type
On Fri, Feb 20, 2009 at 3:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
create table foo(a int, b int);
postgres=# create function rfoo() returns setof foo as $$ begin return
query select foo from foo; end; $$ language plpgsql;
Use select * from
On Fri, Feb 20, 2009 at 3:25 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Fri, Feb 20, 2009 at 3:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
create table foo(a int, b int);
postgres=# create function rfoo() returns setof foo as $$ begin return
query
It looks like for row-wise comparison, only the first column is used
for generating the expected row count. This can lead to bad plans in
some cases.
Test case (takes seconds to minutes hardware depending):
create table range as select v as id, v % 500 as key, now() +
((random() * 1000) ||
On Mon, Mar 2, 2009 at 4:43 PM, Merlin Moncure mmonc...@gmail.com wrote:
It looks like for row-wise comparison, only the first column is used
for generating the expected row count. This can lead to bad plans in
some cases.
Test case (takes seconds to minutes hardware depending):
create
On Mon, Mar 2, 2009 at 8:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
It looks like for row-wise comparison, only the first column is used
for generating the expected row count.
[ shrug... ] Short of multi-column statistics, it's hard to see how to
do
On Fri, Mar 20, 2009 at 4:08 PM, Bruce Momjian br...@momjian.us wrote:
Bruce Momjian wrote:
Bruce Momjian wrote:
Here are some of the emails I consider open for 8.4:
http://momjian.us/cgi-bin/pgsql/open
(Same email, using updated subject line.)
mbox download URL fixed.
Let me
On Sat, Mar 21, 2009 at 12:11 PM, Magnus Hagander mag...@hagander.net wrote:
The open items list for 8.4 has
*) PQinitSSL broken in some use casesf
This should be addressed. Andrew C proposed a few different ways to
do it and supplied patches. Pick one and apply it.
*) Re: [HACKERS] patch to
On Sat, Mar 21, 2009 at 12:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
The open items list for 8.4 has
* problems with Windows global namespace
I propose we move this over to the TODO list instead.
Agreed. In general, any issue that already exists
On Fri, Mar 27, 2009 at 11:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
PQinitSSL broken in some use cases
This is a hard case. It's arguably a bug fix, but not one that we could
back-patch. I think we would have applied it by now if there were
consensus on which solution to pick.
I think the
On Fri, Mar 27, 2009 at 9:38 PM, Bruce Momjian br...@momjian.us wrote:
I have applied the attached patch which does several things:
o documents that libssl _and_ libcrypto initialization is
turned off by PQinitSSL(0)
o clarified cases where this behavior is important
On Sat, Mar 28, 2009 at 9:23 AM, Merlin Moncure mmonc...@gmail.com wrote:
It is still a bug in the sense that it is impossible to properly
initialize crypto features in some scenarios. A doc patch (which I
Meant to say: 'your doc patch
merlin
--
Sent via pgsql-hackers mailing list (pgsql
On Sat, Mar 28, 2009 at 4:26 PM, Bruce Momjian br...@momjian.us wrote:
Andrew Chernow wrote:
Tom Lane wrote:
This is just a rehash of one of the patches that was discussed earlier.
There wasn't consensus for it then, and there's not now.
I am personally out of ideas. It feels like this
On Sun, Mar 29, 2009 at 1:56 PM, Bruce Momjian br...@momjian.us wrote:
I think this is where we got stuck because extending libpq with a new
function is a larger API change, and not having a clear plan of what
initialization stuff we might need in the future, it seems unwise, and
also perhaps
On Mon, Mar 30, 2009 at 10:22 AM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Mar 30, 2009 at 9:36 AM, Andrew Chernow a...@esilo.com wrote:
Tom Lane wrote:
I personally would be happy with the two-argument function solution.
I modified my previous patch to use a two-argument function
On Mon, Mar 30, 2009 at 3:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I guess that'd work but it might be overkill.
The real bottom line is that *all* the proposals for generic init
functions are overkill. We have no evidence that we need one and
no
On 10/11/06, Marco Serantoni [EMAIL PROTECTED] wrote:
I'm evaluating of use postgresql but for local law requirements is
needed for the access of some kind of data (sensitive) a log of the
accesses (Auditing) is a feature available in many databases but i've
seen that lacks in PostgreSQL, there
On 10/12/06, Marco Serantoni [EMAIL PROTECTED] wrote:
I'm evaluating of use postgresql but for local law requirements is
needed for the access of some kind of data (sensitive) a log of the
accesses (Auditing) is a feature available in many databases but i've
seen that lacks in PostgreSQL,
On 10/12/06, Tom Lane [EMAIL PROTECTED] wrote:
[ This is off-topic for -performance, please continue the thread in
-hackers ]
This proposal seems to deliberately ignore every point that has been
made *against* doing things that way. It doesn't separate the hints
from the queries, it doesn't
On 10/12/06, Andrew Sullivan [EMAIL PROTECTED] wrote:
On Thu, Oct 12, 2006 at 11:25:25AM -0500, Jim C. Nasby wrote:
Yes, but it does one key thing: allows DBAs to fix problems *NOW*. See
also my comment below.
If I may argue in the other direction, speaking as one whose career
(if we may be
On 10/15/06, Anon Mous [EMAIL PROTECTED] wrote:
Would it be possible to combine a special memcache implementation of
memcache with a Postgresql interface wrapper?
have you seen
http://people.freebsd.org/~seanc/pgmemcache/
merlin
---(end of
On 10/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Using memcache, I've had problems with consistency brought right to
the front. Both of these have failed me:
1) When updating a PostgreSQL record, I invalidate the memcache record.
If another process comes along in parallel
On 10/15/06, Luke Lonergan [EMAIL PROTECTED] wrote:
Martijn,
The killer use-case we've identified is for the scattered I/O associated
with index + heap scans in Postgres. If we can issue ~5-15 I/Os in advance
when the TIDs are widely separated it has the potential to increase the I/O
speed by
On 10/19/06, Krycek [EMAIL PROTECTED] wrote:
The proposed syntax is:
GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW
TABLES IN public TO phpuser;
GRANT SELECT ON NEW TABLES IN public TO phpuser;?
What does NEW TABLES mean in this context?
the point is to allow tables
On 10/20/06, Jeremy Drake [EMAIL PROTECTED] wrote:
I noticed something odd when trying to use the row-wise comparison
mentioned in the release notes for 8.2 and in the docs
http://developer.postgresql.org/pgdocs/postgres/functions-comparisons.html#ROW-WISE-COMPARISON
This sets up a suitable
On 10/20/06, Tom Lane [EMAIL PROTECTED] wrote:
So far I've seen no evidence that async I/O would help us, only a lot
of wishful thinking.
is this thread moot? while researching this thread I came across this
article: http://kerneltrap.org/node/6642 describing claims of 30%
performance boost
On 10/21/06, Martijn van Oosterhout kleptog@svana.org wrote:
On Fri, Oct 20, 2006 at 03:04:55PM -0400, Merlin Moncure wrote:
On 10/20/06, Tom Lane [EMAIL PROTECTED] wrote:
So far I've seen no evidence that async I/O would help us, only a lot
of wishful thinking.
is this thread moot? while
On 1/10/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
What about a Mingw or VC++ psql with a BCC libpq? Is it possible to
link something like that?
It would be nice to have the libpq at least able to pass the regression
tests.
you can use microsoft/mingw compiled DLL files but not library
I've never really been very happy with the decision early on in the
development of nested transactions to use savepoints in the way they
were implemented in the command structure. Savepoints are nearly
useless for sql scripting because there is no way to probe a
transaction and handle error
On 1/19/07, Tom Lane [EMAIL PROTECTED] wrote:
Merlin Moncure [EMAIL PROTECTED] writes:
I suspect the savepoint command is almost never used
outside of oracle compatibility efforts.
Last I heard, we implemented it because it is in the SQL standard.
I have no idea (nor do I much care) whether
On 1/22/07, Csaba Nagy [EMAIL PROTECTED] wrote:
On Sat, 2007-01-20 at 18:08, Merlin Moncure wrote:
[snip]
To be honest, I'm not a huge fan of psql tricks (error recovery being
another example) but this could provide a solution. in your opnion,
how would you use \if to query the transaction
On 1/21/07, Tom Lane [EMAIL PROTECTED] wrote:
Jaime Casanova [EMAIL PROTECTED] writes:
On 1/21/07, Simon Riggs [EMAIL PROTECTED] wrote:
- continue on error i.e. COMMIT can/might succeed - though there are
still cases where it cannot, such as a serializable exception.
and what should be the
On 1/22/07, Simon Riggs [EMAIL PROTECTED] wrote:
Could you post an example, just so we're all clear what the problems
are? I thought I understood what you are requesting; I may not.
ok,
The short version is I would like the ability to run some sql commands
and recover the transaction if an
On 1/22/07, Martijn van Oosterhout kleptog@svana.org wrote:
we're talking about psql, maybe all we need to do is create the
commands in psql:
\begin_nest
\commit_nest
\rollback_nest
That would work if we could rollback conditionally on failure (like
on_error_rollback but with definable
On 1/22/07, Tom Lane [EMAIL PROTECTED] wrote:
I'm getting tired of repeating this, but: neither of you have said
anything that doesn't appear to me to be handled by ON_ERROR_ROLLBACK.
What exactly is lacking in that feature?
* the ability to span the savepoint across multiple statements.
* the
On 1/22/07, Martijn van Oosterhout kleptog@svana.org wrote:
I don't understand this either. Everything you can do with nested
transactions you can also do with savepoints, so I'm really not
understand what the limitations are?
Actually, looking at the savepoint documentation, it looks like
On 1/22/07, Dawid Kuroczko [EMAIL PROTECTED] wrote:
On 1/22/07, Tom Lane [EMAIL PROTECTED] wrote:
The short version is I would like the ability to run some sql commands
and recover the transaction if an error occurs.
I'm getting tired of repeating this, but: neither of you have said
On 1/22/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
i think so...Martijn said it best: you can 'rollback' to, but you
can't 'commit' to. The 'commit to' would be the arguably much more
useful way of disposing of a savepoint. But that should be taken up
with sql standards committee :(.
You
On 1/22/07, Joshua D. Drake [EMAIL PROTECTED] wrote:
Or so... :)
Thought I would do a poll of what is happening in the world for 8.3. I have:
Alvaro Herrera: Autovacuum improvements (maintenance window etc..)
Gavin Sherry: Bitmap Indexes (on disk), possible basic Window functions
Jonah Harris:
On 1/24/07, Stephen Frost [EMAIL PROTECTED] wrote:
Sure, all the objects in a given schema should be owned by a role which
all the admins of that schema are members of. I really see this as a
sensible step from ACLs since ownership implies additional permissions
(which can't otherwise be
On 1/24/07, Merlin Moncure [EMAIL PROTECTED] wrote:
when you create them. Table rights almost always follow broad rules
so it only natural to integrate that with schemas somehow...but
admittedly it is awkward to put it into GRANT (and I've thought alot a
bout.
oops :( what I meant to say here
On 1/24/07, Stephen Frost [EMAIL PROTECTED] wrote:
err, what proposal wasn't touching the GRANT syntax at all but rather
right, but the original proposal did:
# %Allow GRANT/REVOKE permissions to be applied to all schema objects
with one command
which was more or less (with the NEW TABLES
On 1/25/07, Jim C. Nasby [EMAIL PROTECTED] wrote:
decibel=# select version();
PostgreSQL 8.3devel on i386-apple-darwin8.8.2, compiled by GCC
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5363)
decibel=# select box '((0,0),(2,2))' ~ point '(1,1)';
ERROR: operator does
On 2/6/07, Merlin Moncure [EMAIL PROTECTED] wrote:
around 6:30 this morning, I started getting the following messages in my log:
Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
status of transaction 51911
Feb 6 06:34:35 mojo postgres[1128]: [2-1] :: ERROR: could
On 2/6/07, Stefan Kaltenbrunner [EMAIL PROTECTED] wrote:
Merlin Moncure wrote:
On 2/6/07, Merlin Moncure [EMAIL PROTECTED] wrote:
around 6:30 this morning, I started getting the following messages in
my log:
Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
status
On 2/6/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
actually, here is some more relevant bits from the log.
Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum:
processing database template0
Feb 6 06:31:33 mojo postgres[1088]: [2-1] :: ERROR: could not access
status of
n 2/6/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
Merlin Moncure wrote:
ya, it doesn't seem to match, as this seems to be repeating quite
regularly. interesting that my 'clog' files start at 06B6 and count
up. 0207 is way off the charts.
a lot of applications are hitting this database
On 2/6/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
Merlin Moncure wrote:
On 2/6/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
actually, here is some more relevant bits from the log.
Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum:
processing database template0
Feb 6 06:31
It would be great to be able to join to update, returning, etc. It
looks like the code was deliberately tied off as-is and I was
surprised not to see a todo for this.
the basic idea is to be able to do things like:
select * from (update foo set id = 1 returning *) q;
which currently syntax
On 2/7/07, Joshua D. Drake [EMAIL PROTECTED] wrote:
Simon Riggs wrote:
Heap Only Tuples (HOT) is a simplification of earlier proposals for
improving the way the server handles frequent updates, based upon what's
been learned and feedback received.
Uhmmm... how often is that the case? Don't
601 - 700 of 1941 matches
Mail list logo
