On Sun, 2008-05-18 at 22:17 -0700, David Fetter wrote:
On Mon, May 19, 2008 at 12:21:20AM -0400, Gregory Stark wrote:
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
Also, it seems there are no infinite recursion detection:
# with recursive x(level, parent, child) as (
select
Before this patch, pl/python will not do the right thing if OUT
parameters are present
Hannu
Index: plpython/plpython.c
===
RCS file: /projects/cvsroot/pgsql/src/pl/plpython/plpython.c,v
retrieving revision 1.106
perhaps from better disk cache usage.
For me pg_compresslog seems to be a winner even if it just does not
degrade performance.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http
many bytes the current (multibyte) character covers.
The length is still easy to find out for UTF8 encoding, so it may be
feasible to write UTF8MatchText() that is still faster than
MBMatchText().
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast)---
TIP 7: You can help support
Ühel kenal päeval, L, 2006-08-12 kell 10:59, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane:
Insert points to the next byte to be written within the internal WAL
buffers. The byte(s) preceding it haven't necessarily
Ühel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, K, 2006-08-09 kell 12:56, kirjutas Simon Riggs:
Methinks it should be the Write pointer all of the time, since I can't
think of a valid reason for wanting to know where
.
The function to retrieve the 8-byte trx id will look exatly the same
from userland in both cases.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Hannu Krosing
Database
the pg_sync_txid() issued by pg_dump instead pg_dumpall?
--
marko
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Hannu Krosing
Database Architect
Skype Technologies
of the *table* but still has to scan full *indexes*.
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
---(end of broadcast
problem for slony.
That is unless thera are some bugs or thinkos of its own in this
patch :)
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
, but avoid trying to hack
around this. It would make the bug even more resistent :-)
We have been trying to advocate such approach, but so far with modest results :(
--
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me
Ühel kenal päeval, E, 2006-05-15 kell 17:21, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
Sven Suursoho wrote:
As for testing in actual pl/python build environment, we had objections
from
leading postgresql Tom Lane that even if we do test it at build time,
a determined
Ühel kenal päeval, R, 2006-05-05 kell 09:20, kirjutas Joshua D. Drake:
I think that a less confusing way of saying it would be :
Generators crash if python version used is 2.4.x and it is compiled
with asserts.
Currently only known linux distributions to distibute such
Ühel kenal päeval, N, 2006-05-04 kell 18:21, kirjutas Sven Suursoho:
Hi,
Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane [EMAIL PROTECTED]:
Sven Suursoho [EMAIL PROTECTED] writes:
Unfortunately, there is still one problem when using unpatched python,
caused by too aggressive assert.
Ühel kenal päeval, P, 2006-04-30 kell 14:43, kirjutas Tom Lane:
Sven Suursoho [EMAIL PROTECTED] writes:
So, what about this in configure:
if --with-python test_iterator_app_crashes
# errcode(FEATURE_NOT_SUPPORTED), errmsg(patch your python)
disable_iterator_feature
fi
Testing
Ühel kenal päeval, N, 2006-04-27 kell 10:17, kirjutas Bruce Momjian:
Sorry, I have to revert this patch because it is causing crashes in the
plpython regression tests. Would you please run those tests, fix the
bug, and resubmit. Thanks.
Where exactly does it crash ?
Please tell us the
Ühel kenal päeval, L, 2006-04-15 kell 17:59, kirjutas Sven Suursoho:
1) named parameters additionally to args[]
2) return composite-types from plpython as dictionary
3) return result-set from plpython as list, iterator or generator
Test script attached (patch-test.sql) but not integrated to
On K, 2005-08-17 at 15:40 -0400, Tom Lane wrote:
Saatja:
Tom Lane [EMAIL PROTECTED]
Kellele:
Bruce Momjian
pgman@candle.pha.pa.us, Hannu
Krosing [EMAIL PROTECTED], Neil Conway
[EMAIL PROTECTED], pgsql-
[EMAIL PROTECTED
On R, 2005-08-12 at 15:47 -0400, Bruce Momjian wrote:
This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Is there any particular reason for not putting it in 8.1 ?
--
Hannu Krosing [EMAIL PROTECTED]
---(end
On P, 2005-07-03 at 12:19 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Ok, this is a new version of the vacuum patch with the following changes
following some suggestions in this thread.
The more I look at this, the uglier it looks ... and I still haven't
seen any
On E, 2005-07-04 at 10:24 +0300, Hannu Krosing wrote:
On P, 2005-07-03 at 12:19 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Ok, this is a new version of the vacuum patch with the following changes
following some suggestions in this thread.
The more I look
On E, 2005-05-23 at 11:42 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
I can't think of any other cases where it could matter, as at least the
work done inside vacuum_rel() itself seema non-rollbackable.
VACUUM FULL's tuple-moving is definitely roll-back-able, so it might
the
work done inside vacuum_rel() itself seema non-rollbackable.
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
On E, 2005-05-23 at 11:42 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
I can't think of any other cases where it could matter, as at least the
work done inside vacuum_rel() itself seema non-rollbackable.
VACUUM FULL's tuple-moving is definitely roll-back-able, so it might
the patch. Unless other readers
would like to follow on.
I hope you will you will get that time before 8.1 ships :)
--
Hannu Krosing [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Bruce Momjian kirjutas E, 17.11.2003 kell 03:58:
OK, let me give you my logic and you can tell me where I am wrong.
First, how many backend can a single write process support if all the
backends are doing insert/update/deletes? 5? 10? Let's assume 10.
Second, once we change write to
Rod Taylor kirjutas L, 08.11.2003 kell 18:55:
A general re-organization of Alter Table. Node wise, it is a
AlterTableStmt with a list of AlterTableCmds. The Cmds are the
individual actions to be completed (Add constraint, drop constraint, add
column, etc.)
Processing is done in 2 phases.
Alvaro Herrera kirjutas R, 14.11.2003 kell 16:17:
On Fri, Nov 14, 2003 at 08:59:05AM -0500, Dave Cramer wrote:
I tried the current patch on a RC2 release, and I noticed one
undesirable side affect.
Modifying a column moves it to the end. In high availability situations
this would
Peter Eisentraut kirjutas K, 12.11.2003 kell 21:02:
Rod Taylor writes:
ALTER TABLE tab ADD COLUMN col DEFAULT 3, ADD CHECK (anothercol 3);
The above combinational syntax is commented out in gram.y. The
support framework is used in both the above and below items, but
30 matches
Mail list logo
