Michael Meskes wrote:
Hans,
nce Jaime already asked for a use case, just a few small comments from
me.
@@ -4,6 +4,7 @@
#include "postgres_fe.h"
#include
+#include
This is not portable. You don't want to include this header.
Did I see this right that you use the statement cache
hello ...
just as a background info: this will have some positive side effects on
embedded C programs which should be portable.
informix, for instance, will also return a row count on those commands.
regards,
hans
Pavel Stehule wrote:
2009/12/28 Boszormenyi Zoltan :
Hi,
atta
*snip*
One pretty major fly in the ointment is that neither Hot Standby nor
Streaming Replication has been committed or shows much sign of being
about to be committed. I think this is bad. These are big features
that figure to have some bugs and break some things. If they're not
committed in
hello ...
as my day has worked out quite nicely up to know i thought to f... it up
and post a new concept which has been requested by a customer. the goal
is to collect some feedback, ideas and so on (not to be mixed up with
"flames").
we have funding for this and we are trying to sort out how
hi there ...
for this work i will include you in my evening prayers for at least one
week.
i know there has been a lot of discussion about this but what you just
posted it excellent and more important: USEFUL to many people.
i had something else in mind recently as well: virtual indexes. it w
Jeff Janes wrote:
Will statement_timeout not suffice for that use case?
we tried to get around it without actually touching the core but we
really need this functionality.
patching the core here is not the primary desire we have. it is all
about modeling some functionality which was truly mis
Tom Lane wrote:
Josh Berkus writes:
Jeff,
Will statement_timeout not suffice for that use case?
Well, currently statement_timeout doesn't affect waiting for locks.
Sure it does.
And as a DBA, I don't think I'd want the same timeout for executing
queries as for
Tom,
On behalf of the entire PostgreSQL team here in Austria I want to wish
you a happy birthday.
We hope that you fill be a vital part of PostgreSQL for many years to come.
Best regards,
Hans-Jürgen Schönig + team
--
Cybertec Schoenig & Schoenig GmbH
Reyergasse 9 / 2
A-2700 Wiener
consider doing with partly with gist
and partly with a btree.
is there any option to adapt gist in a way that a combined index would
make sense here?
many thanks,
hans
Heikki Linnakangas wrote:
Hans-Juergen Schoenig -- PostgreSQL wrote:
my knowledge of how gist works
Martijn van Oosterhout wrote:
On Mon, Aug 31, 2009 at 04:06:22PM +0200, Hans-Juergen Schoenig -- PostgreSQL
wrote:
ok, i thought it would be something gist specific i was not aware of.
the golden question now is: i am looking for the cheapest products given
a certain text in an insane
Andrew Dunstan wrote:
Werner Echezuria wrote:
Hi, I have a code in which I translate some code from sqlf to sql, but
when it comes to yy_parse the server crashes, I have no idea why,
because it works fine in other situations.
I don't understand why you're doing what you're doing this way.
Tom Lane wrote:
Hans-Juergen Schoenig -- PostgreSQL writes:
what we basically expected here is that Postgres will scan the table
using the index to give us the cheapest products containing the words we
are looking for.
i am totally surprised to see that we have to fetch all products given
hello everybody,
we are seriously fighting with some planner issue which seems to be
slightly obscure to us.
we have a table which is nicely indexed (several GB in size).
i am using btree_gist operator classes to use a combined index including
an FTI expression along with a number:
db=# \d p
Hans-Juergen Schoenig -- PostgreSQL wrote:
hello,
this patch has not made it through yesterday, so i am trying to send
it again.
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector to
hello,
this patch has not made it through yesterday, so i am trying to send it
again.
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector to table format which is really nice for text
pro
hello,
i made a small patch which i found useful for my personal tasks.
it would be nice to see this in 8.5. if not core then maybe contrib.
it transforms a tsvector to table format which is really nice for text
processing and comparison.
test=# SELECT * FROM tsvcontent(to_tsvector('english',
hello everybody,
from my side the goal of this discussion is to extract a consensus so
that we can go ahead and implement this issue for 8.5.
our customer here needs a solution to this problem and we have to come
up with something which can then make it into PostgreSQL core.
how shall we proce
I tend to think there should be protocol level support for options
like this but that would require buy-in from the interface writers.
how would you do it?
if you support it on the protocol level, you still need a way to allow
the user to tell you how ...
i would see WAIT for DELETE, UP
hello greg,
the thing with statement_timeout is a little bit of an issue.
you could do:
SET statement_timeout TO ...;
SELECT FOR UPDATE ...
SET statement_timeout TO default;
this practically means 3 commands.
the killer argument, however, is that the lock might very well happen
ways af
hello everybody,
i would like to propose an extension to our SELECT FOR UPDATE mechanism.
especially in web applications it can be extremely useful to have the
chance to terminate a lock after a given timeframe.
i would like to add this functionality to PostgreSQL 8.5.
the oracle syntax is qui
abdelhak benmohamed wrote:
hello,
here more of details
I have a set of transaction. Naturally, the transactions execute
themselves in competition. But I would want to give to every
transaction a priority. Thus the transaction more priority must
execute itself in first.
I thought, as
Josh Berkus 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 make more of a
difference in the
Peter Eisentraut wrote:
I seem to recall that there was general support for installing a smaller
default postgresql.conf file with only, say, a dozen parameters mentioned for
initial tuning. The complete file can stay as a sample. Any objections to
that? (Let's not discuss quite yet exactly
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 *
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.
Tom Lane wrote:
I've pretty much finished the project I got a bee in my bonnet about
last week, which is to teach SELECT DISTINCT how to (optionally) use
hashing for grouping in the same way that GROUP BY has been able to do
for awhile.
There are still two places in the system that hard-wire the
Simon Riggs wrote:
On Mon, 2008-07-07 at 16:26 -0700, David Fetter wrote:
On Mon, Jul 07, 2008 at 06:46:29PM -0400, Andrew Dunstan wrote:
For the record, I agree with Jan's suggestion of passing a pointer
to the parse tree, and offline gave David a suggestion verbally as
to how this cou
good morning everybody,
i know that this is really a hot potato on the mailing list but i think
it is useful to discuss this issue.
in the past few months we have been working with a customer to improve
evgen's CONNECT BY patch.
as we have a nice and promising WITH RECURSIVE patch the original
hello david,
i did some quick testing with this wonderful patch.
it seems there are some flaws in there still:
test=# explain select count(*)
test-# from ( WITH RECURSIVE t(n) AS ( SELECT 1 UNION ALL
SELECT DISTINCT n+1 FROM t )
test(# SELECT * FROM t WHERE n < 500
On Jun 28, 2008, at 11:39 AM, Gregory Stark wrote:
"Hans-Juergen Schoenig" <[EMAIL PROTECTED]> writes:
why do i get a different timezone just because of adding one more
century?
i cannot see an obvious reason.
What version of Postgres and what setting of TZ?
--
hello everybody ...
i am sitting here in a training and i am wondering about the
following issue ...
test=# select now() + '3 years 2 decades 4000 seconds 9
minutes'::interval;
?column?
---
2031-06-28 11:58:35.052423+02
(1 row)
test=# select now() +
Alvaro Herrera wrote:
Hans-Juergen Schoenig wrote:
test=# create role xy LOGIN;
CREATE ROLE
test=# grant connect on database test to xy;
GRANT
test=# drop role xy;
ERROR: role "xy" cannot be dropped because some objects depend on it
DETAIL: access to database test
this is
Gregory Stark wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Couldn't we just have it pay attention to the existing
max_stack_depth?
Recursive query does not consume stack. The server enters an infinite
loop without consuming stack. Stack-depth error does not happen.
good morning,
some days ago i have fallen over an issue which feels more or less like
a bug. consider:
test=# create role xy LOGIN;
CREATE ROLE
test=# grant connect on database test to xy;
GRANT
test=# drop role xy;
ERROR: role "xy" cannot be dropped because some objects depend on it
DETAI
Joshua D. Drake wrote:
Hans-Juergen Schoenig wrote:
regards, tom lane
overhead is not an issue here - if i lose 10 or 15% i am totally fine
as long as i can reduce vacuum overhead to an absolute minimum.
overhead will vary with row sizes anyway - this is not the point.
I
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
... Keep in mind you're proposing to make everything run 3% slower instead of
using that 3% i/o bandwidth headroom to run vacuum outside the critical path.
I think that's actually understating the problem. Assuming this is a
64
hello everybody,
i know that we have discussed this issue already. my view of the problem
has changed in the past couple of weeks, however. maybe other people had
similar experiences.
i have been working on a special purpose application which basically
looks like that:
- 150.000 tables (f
Hannu Krosing wrote:
A question to all pg hackers
Is anybody working on adding pipelining to set returning functions.
How much effort would it take ?
Where should I start digging ?
i asked myself basically the same question some time ago.
pipelining seems fairly impossible unless we ban j
"Decibel!" <[EMAIL PROTECTED]> writes:
If we're going to make this a ./configure option, ISTM we should
do the same
with XID size as well. I know there are high-velocity databases
that could use
that.
Keep in mind we just changed things so that read-only transactions
don't
consume xid
On Feb 18, 2008, at 9:09 PM, Peter Eisentraut wrote:
Justin wrote:
Now for my question It does not appear PostgreSQL does not have an Ad
Hoc Indexes ability where the Query planner will create an in memory
index based on the Select, Update, Insert or Delete commands.
How is that supposed to
e the data.
this is what happens during an index scan.
i suggest to step tnrough this process with a debugger to see what is
going on.
hans
On Feb 17, 2008, at 5:13 PM, Suresh wrote:
Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
On Feb 17, 2008, at 4:33 PM, Suresh wrote:
[
ve
to be done is to get the record from disk to check visibility and
other columns.
best regards,
hans-juergen schoenig
--
Cybertec Schönig & Schönig GmbH
PostgreSQL Solutions and Support
Gröhrmühlgasse 26, 2700 Wiener Neustadt
Tel: +43/1/205 10 35 / 340
www
On Jan 25, 2008, at 7:27 AM, Decibel! wrote:
On Wed, Jan 23, 2008 at 05:50:02PM -0500, Tom Lane wrote:
Simon Riggs <[EMAIL PROTECTED]> writes:
From looking at how Oracle does them, autonomous transactions are
completely independent of the transaction that originates them
-- they
take a new
On Jan 28, 2008, at 6:14 PM, Simon Riggs wrote:
On Sun, 2008-01-27 at 21:04 -0500, Tom Lane wrote:
[ redirecting thread to -hackers ]
Neil Conway <[EMAIL PROTECTED]> writes:
On Sun, 2008-01-27 at 21:54 +, Gregory Stark wrote:
I liked the "synchronized_sequential_scans" idea myself.
I
On Jan 25, 2008, at 1:01 PM, Peter Eisentraut wrote:
What about a feature to set a default tablespace just for indexes?
I have
been told that this was originally proposed when tablespaces where
designed,
but did not end up being implemented. Does anyone recall the
details? I
have had p
sure, but this can become really tedious for 1024 partitions,
Well, managing 1024 partitions manually is a tedious job, no matter
what grammar you take: You'll have to deal with 1024 different
partition names.
What do you need so many partitions for?
imagine a structure which is pa
I think Simon Riggs is already working on that idea. This one is
fairly easy to implement. I think these are some of the features
only a time-stamp based database can implement. I think database
standards were formed during the time, when the data consistency
was provided with Lock based
hello ...
i guess there is no formal proposal yet but there are some ideas
around and some major challenges have been discussed already.
i think simon riggs was planning to work on it in the future.
the basic idea here is to have the option to create a "snapshot"
which then stays in the data
AFAICS, maximum number of command ids is actually 2^32-1, or over 4
billion. Are you sure you bumped into that limit and not something
else?
What's the error message you're getting?
What version of Postgres is this? PG 8.3 will have another related
limit
on the number of combocids you can
at the moment i am working on an application which is supposed to run
extremely large transactions (a lot of server side stored procedure
stuff which can hardly be split into small transactions for
visibility reasons).
so, from time to time it happens that i exceed my CommandCounter (>
2.00
On Aug 29, 2007, at 6:44 PM, Tom Lane wrote:
Hans-Juergen Schoenig <[EMAIL PROTECTED]> writes:
i came across some interesting behavior of pg_stats and i am not sure
if this is something we should treat the way we do it.
Setting target zero means "expend no work on this column". In
i came across some interesting behavior of pg_stats and i am not sure
if this is something we should treat the way we do it.
consider:
test_hans=# select * from pg_stats where attname = 'id' and tablename
= 't_testhugo';
schemaname | tablename | attname | null_frac | avg_width |
n_distinct
Make a loadable PL "plpgsqlsec" or something like that that's just
a thin wrapper around the plpgsql call handler, and all it does is
decrypt the source text.
perfect idea, simple perfect.
i did not consider that yet.
i was hoping for some enlightenment like that.
would be a nice module for
The basic problem is this: if you have to decrypt the code in order
to give it to a compiler (PL/pgSQL, Java, Perl, ...) then there is
a point in time where the source code is in plaintext form - it
would be trivial to add an fprintf( stderr, "%s", plainTextForm )
to the PL handler to ste
On Aug 9, 2007, at 5:03 PM, Greg Smith wrote:
On Thu, 9 Aug 2007, Andrew Dunstan wrote:
There are also some fairly impressive code obfuscators about, that
your clients might find useful.
All they really need is to find a sufficiently clever PL/Perl
programmer.
we should make this a PL
On Aug 9, 2007, at 4:47 PM, korry.douglas wrote:
the idea is basically to hide codes - many companies want that and
ask for it again and again.
Hide code from who (or is that whom?)?
the code should be hidden from the guy who is actually executing the
function.
so:
some user i
On Aug 9, 2007, at 4:34 PM, Peter Eisentraut wrote:
Am Donnerstag, 9. August 2007 16:09 schrieb Hans-Juergen Schoenig:
the idea is basically to hide codes - many companies want that and
ask for it again and again.
If you want to design a security feature, you need to offer a
threat and
.
maybe we can agree on a nice mechanism here which will be implemented
then.
hans
On Aug 9, 2007, at 3:57 PM, Andrew Dunstan wrote:
Hans-Juergen Schoenig wrote:
hello everybody,
one of our customers wants to store the code of interpreted
procedures (PL/pgSQL, PL/Perl) and so in
hello everybody,
one of our customers wants to store the code of interpreted
procedures (PL/pgSQL, PL/Perl) and so in an encrypted way.
so the idea we had to add one more column to pg_proc telling us
whether prosrc is encrypted or not. people could chose then whether
to crypt codes there or
is it good to allow locks on system tables at all?
i am not so sure. have seen some disaster in the past with that. just
consider somebody placing ACCESS EXCLUSIVE LOCK on a system table. it
is basically denial of service.
best regards,
hans
On Jul 10, 2007, at 3:
On Jul 9, 2007, at 12:24 PM, Marko Kreen wrote:
On 7/9/07, Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
does anybody remember why threaded python is not allowed on some
flavors of BSD?
AFAIR the problem is they use separate libc for threaded things,
and main postgres is (and w
hello all ...
does anybody remember why threaded python is not allowed on some
flavors of BSD?
i was surprised to read this in the configure script ...
# threaded python is not supported on bsd's
echo "$as_me:$LINENO: checking whether Python is compiled with thread
support" >&5
echo $ECHO_N
shieldy wrote:
> Hi, I wanto joinin the developer group of postgresql。
> But, I just donot know how to put the first step, as I installed the
> postgresql, and also get the postgresql code. after that, I also
> installed the cygwin on my computer( as my os is windows xp). but now
> I wonder what's
Simon Riggs wrote:
On Thu, 2007-02-01 at 09:15 +0100, Hans-Juergen Schoenig wrote:
Right now max_locks_per_transactions defines the average number of locks
taken by a transaction. thus, shared memory is limited to
max_locks_per_transaction * (max_connections + max_prepared_transactions
Right now max_locks_per_transactions defines the average number of locks
taken by a transaction. thus, shared memory is limited to
max_locks_per_transaction * (max_connections + max_prepared_transactions).
this is basically perfect. however, recently we have seen a couple of
people having troubl
oh sorry, i think i missed that one ...
many thanks,
hans
On Dec 19, 2006, at 3:42 PM, Stefan Kaltenbrunner wrote:
Hans-Juergen Schoenig wrote:
[...]
a quick fix is to prevent the language from freeing the tuple
twice - this should safely prevent the core dump here.
we still
one of our customers here found a bug in PL/pgSQL.
this is how you can create this one:
CREATE OR REPLACE FUNCTION "public"."make_victim_history" () RETURNS
trigger AS $body$ DECLARE
schemarec RECORD;
exec_schemaselect text;
curs2 refcursor;
BEGIN
exec_schemaselect := 'SELECT nspname
On Sep 4, 2006, at 7:04 PM, Bruno Wolff III wrote:
On Mon, Sep 04, 2006 at 17:19:37 +0200,
Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
i thought about creating an index on the expression but the problem
is that this is hardly feasable.
in 8.0 (what i have here) this would blo
problem for some other issues as well. an index
might not be flexible enough :(.
many thanks,
hans
On Sep 4, 2006, at 4:57 PM, Tom Lane wrote:
Hans-Juergen Schoenig <[EMAIL PROTECTED]> writes:
consider the following:
SELECT some_timestamp::dat
i am looking at some corner case which might also cause troubles for
other people.
consider the following:
SELECT some_timestamp::date FROM very_large_table GROUP BY
some_timestamp::date
my very_large_table is around 1billion entries.
the problem is: the planner has a problem here as it is
Tom Lane wrote:
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
Bruce Momjian wrote:
Well, the patch was submitted in time, and it is a desired feature. If
we want to hold it for 8.3 due to lack of time, we can, but I don't
think we can decide now that it must wait.
well
As my last mail did not seem to go through here one more try ...
When looking at some fairly complex SQL stuff I came across some
interesting issue which is a bit surprising to me:
CREATE OR REPLACE FUNCTION xy() RETURNS SETOF record AS $$
SELECT relname::text, relpages::int4
On 21 Feb 2006, at 10:42, Martijn van Oosterhout wrote:
On Tue, Feb 21, 2006 at 10:02:58AM +0100, Albe Laurenz wrote:
Thank you also for drawing my attention to pg_service.conf - I
have not
been aware of it.
There are two 'shortcomings':
- It still means that you have to change the config fi
On Dec 5, 2005, at 4:17 AM, Tom Lane wrote:
Greg Stark <[EMAIL PROTECTED]> writes:
Plan stability is also an important feature, especially for OLTP
systems which have hard real-time requirements. OLTP systems
typically
don't care about getting the "best" plan for a query, only a plan
that
wouldn't it be more flexible to define a multiplicator or some sort of bool flag on a per object level?oracle hints are a total overkill and i agree with tom that usually people will abuse this feature.if we had a per object flag the actual planner hint can be decoupled from the actual query (i don
absolutely - the main advantage of the syntax tweak is that you can
add parameters more easily.
best regards,
hans
On 22 Sep 2005, at 21:25, Jim C. Nasby wrote:
On Wed, Sep 21, 2005 at 11:31:42AM -0400, Tom Lane wrote:
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTE
alvora,
what concerns me here: this is a sun system and the problem happened
during normal operation.
there should not be a recovery related operation. something which is
also interesting: there are two corrupted pages in there (page number
22 and 26).
strange thing :(.
thanks a lot,
77 matches
Mail list logo
