possible to lose some changes if we did this together with updating info
for pg_stat_user_tables/pg_statio_user_tables ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql
something. Can you
describe a use case where this would be beneficial?
-Kevin
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
, as physical
files already have this in terms of file ctime/mtime/atime
Side question: is it impractical to backup via pg_dump a hot standby
because of query conflict issues?
merlin
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services
clock changes is also very relevant. Since
Postgres has the capability to give a better answer about what is in the
file, it would be best to use that.
-- m. tharp
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
sample case for tracking latest dml,
except that in this particular corner case you can arrange for this
yourself.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Mon, 2010-03-08 at 21:52 -0500, Andrew Dunstan wrote:
Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
So SPI interface should also be fixed, either from perl side, or maybe
from inside SPI ?
SPI has every right to assume that data it's given is already
from inside SPI ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
this ?
Should there be checks in all text types ?
(probably too expensive)
Or should pl/perl check it's return values for compliance with
server_encoding ?
Or should postgresql itself check that pl-s return what they promise to
return ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL
instead
of all listeners.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
using child tables?
the child tables are there, and they _are_ defined, either implicitly
(using constraints, which constraint exclusion resolves to a set of
child tables) or explicitly, using child table names directly.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability
it to deal with records is inconsistent.
Regards,
Jeff Davis
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Wed, 2009-11-25 at 08:39 -0500, Emmanuel Cecchet wrote:
Hannu Krosing wrote:
On Tue, 2009-11-24 at 10:08 -0500, Emmanuel Cecchet wrote:
Itagaki Takahiro wrote:
I just edited a wiki page for this discussion.
I hope it can be a help.
http://wiki.postgresql.org/wiki
(hidden) partitions.
If the partition tables are visible, some trigger support would be good.
regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing
://www.asterdata.com
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, 2009-11-23 at 18:31 -0500, Greg Smith wrote:
Robert Haas wrote:
I'm fuzzy on what problem this is attempting to solve... as mentioned
in the above guidelines, it's usually good to start with some design
discussions before writing/submitting code.
This has been through some heavy
to also have forms like
COPY func(text) FROM stdin;
and
COPY func(bytea[]) FROM stdin;
for getting a less processed input
should we try to make these kinds of operations a bit more
symmetrical.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services
already, I believe, though
it's so old it still uses abstime :-(
What's wrong with abstime ?
it is valid for timestamps up to 2038-01-19 and it's on-disk size
smaller than other timestamp options
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services
things which don't do connection management it automatically like
pl/proxy does.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Tue, 2009-11-24 at 09:46 +, Thom Brown wrote:
2009/11/24 Hannu Krosing ha...@2ndquadrant.com
On Sun, 2009-11-22 at 18:51 -0500, Tom Lane wrote:
Craig Ringer cr...@postnewspapers.com.au writes:
I do think this comes up often enough that a built
On Tue, 2009-11-24 at 02:56 -0800, Daniel Farina wrote:
On Tue, Nov 24, 2009 at 2:51 AM, Daniel Farina drfar...@gmail.com wrote:
On Tue, Nov 24, 2009 at 2:50 AM, Hannu Krosing ha...@2ndquadrant.com
wrote:
Can't you use existing aggregate function design ?
CREATE AGGREGATE name
On Tue, 2009-11-24 at 03:48 -0800, Daniel Farina wrote:
On Tue, Nov 24, 2009 at 3:25 AM, Hannu Krosing ha...@2ndquadrant.com wrote:
On Tue, 2009-11-24 at 02:56 -0800, Daniel Farina wrote:
On Tue, Nov 24, 2009 at 2:51 AM, Daniel Farina drfar...@gmail.com wrote:
On Tue, Nov 24, 2009 at 2:50
stabilised
enough
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, 2009-11-24 at 09:24 +0200, Heikki Linnakangas wrote:
Greg Smith wrote:
Heikki Linnakangas wrote:
So I guess what I'm asking is: Does anyone see any show-stoppers in
removing VACUUM FULL
Here's the disclaimers attached to the new VACUUM REPLACE implementation
from Itagaki:
implementation concerns.
And maybe even documented ;)
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Thu, 2009-10-29 at 09:32 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
Or maybe we could just extract the hashes form some version of stock
postgresql (say 8.3) and then make those available in contrib under the
name stable_hashes ?
A better name would
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, 2009-10-28 at 12:51 -0700, Jeff Davis wrote:
On Wed, 2009-10-28 at 21:09 +0200, Hannu Krosing wrote:
Is at least the fact that they are undocumented, have changed in the
past, and are likely to change again in the future documented ?
That's a little confusing to me: how do we
On Wed, 2009-10-28 at 15:31 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
I had never checked the docs for hash functions, but I had assumed, that
internal functions are prefixed by pg_ and anything else is public, free
to use functionality.
Sure, it's free to use
error cases caused by charset
incompatibilities ?
and at least
gets the data into the DB where you can hack on it. But it's still
going to be painful for some use cases.
...Robert
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting
On Thu, 2009-09-24 at 17:51 +0900, ning wrote:
Hi all,
I am using psqlodbc to connect to PostgreSQL8.2.4 server on Linux.
The manual says BEGIN TRANSACATION is equlvalent to START
TRANSACTION, but it turns out that they throw different error message
and have different effect to subsequent
are at lower end of table. Or explicitly set
during VF replacement utility.
FSMstrategy = cluster would be the default if clustering is enabled on a
table.
FSMstrategy can change via ALTER TABLE ... WITH (fsm_strategy = ...)
--
Simon Riggs www.2ndQuadrant.com
--
Hannu Krosing
On Fri, 2009-09-18 at 16:24 +0200, Dimitri Fontaine wrote:
Hans-Juergen Schoenig -- PostgreSQL postg...@cybertec.at writes:
Tom,
happy birthday.
+1 from me :)
+1 from me too :D
Regards,
--
dim
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
by VACUUM FULL
if VACUUM FULL is just something that works on a table ends up with
(mostly) compacted one, then doing this CONCURRENTLY should not be
impossible.
If you mean the current version of VACUUM FULL, then this is impossible
indeed.
--
Hannu Krosing http://www.2ndQuadrant.com
that just making sure that pessimal cases don't happen should be
enough, maybe just check for too-much-time-in-transaction after each N
pages touched.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql
On Thu, 2009-09-17 at 10:21 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
On Wed, 2009-09-16 at 21:19 -0400, Tom Lane wrote:
VACUUM FULL CONCURRENTLY is a contradiction in terms. Wishing it were
possible doesn't make it so.
It depends on what do you mean by VACUUM
On Thu, 2009-09-17 at 10:32 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
On Thu, 2009-09-17 at 10:21 -0400, Tom Lane wrote:
because it will break applications that depend on CTID.
Do you know of any such applications out in the wild ?
Yes, they're out there.
How
more grief in this
situation ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
On Thu, 2009-09-17 at 12:36 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
On Thu, 2009-09-17 at 12:18 -0400, Tom Lane wrote:
Or for an update without having to hold a transaction open. We have
recommended this type of technique in the past:
If you need real locking
be tahen from this discussion the other way
round - maybe we should not be afraid of doing null updates during
in-place update
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list
On Wed, 2009-09-16 at 11:10 -0700, Josh Berkus wrote:
Hackers,
Here's the feedback on replacing VACUUM FULL with VACUUM REWRITE:
http://it.toolbox.com/blogs/database-soup/getting-rid-of-vacuum-full-feedback-needed-33959
Of note:
a) To date, I have yet to hear a single person bring up an
have not checked, but I suspect pg_reorg may already be doing
something similar http://pgfoundry.org/forum/forum.php?forum_id=1561
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
, it would have taken some time, but it would have definitely
helped
It would still have caused index bloat, so to get full benefit of it,
one should have finished it up with an equivalent of CONCURRENT REINDEX.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
with extra condition that tuple
is always moved to lowest available free slot.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers
On Wed, 2009-09-16 at 23:53 +0300, Heikki Linnakangas wrote:
Hannu Krosing wrote:
On Wed, 2009-09-16 at 21:23 +0300, Heikki Linnakangas wrote:
2) Another utility that does something like UPDATE ... WHERE ctid ? to
move tuples to lower pages. It will be different from current VACUUM
FULL
of
CREATE OR REPLACE FUNCTION foo(a anyelement, b anyelement)
RETURNS anyarray
regards
Pavel Stehule
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, 2009-09-10 at 08:44 +0300, Hannu Krosing wrote:
maybe just let users say what they mean, so first time we have any and
if we need more then we say same_as(...)
Acutually we could be even more SQL-y and have a more verbose syntax for
pseudotypes by extending the grammar
CREATE
.
(This brings up the whole question of performance impact, which would
have to be thought about and minimized.)
Completely agree - nobody wants a slow COPY command.
regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
On Thu, 2009-09-10 at 21:30 +0200, Pavel Stehule wrote:
2009/9/10 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
2009/9/10 Tom Lane t...@sss.pgh.pa.us:
1. Allow the existing any pseudotype as an input argument type for PLs.
(AFAICS this is simple and painless;
if another type is needed and CAST
exists for getting it
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Thu, 2009-09-10 at 22:15 +0200, Pavel Stehule wrote:
2009/9/10 Hannu Krosing ha...@2ndquadrant.com:
On Thu, 2009-09-10 at 21:35 +0200, Pavel Stehule wrote:
2009/9/10 Tom Lane t...@sss.pgh.pa.us:
Pavel Stehule pavel.steh...@gmail.com writes:
I don't afraid about crashing. Simply I
On Thu, 2009-09-10 at 15:49 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
On Thu, 2009-09-10 at 15:06 -0400, Robert Haas wrote:
It might be possible to make it work, but it's likely to create a lot
of bloat in pg_type, and will make it very difficult to implement
On Thu, 2009-09-10 at 16:48 -0400, Robert Haas wrote:
On Thu, Sep 10, 2009 at 4:38 PM, Hannu Krosing ha...@2ndquadrant.com wrote:
On Thu, 2009-09-10 at 15:49 -0400, Tom Lane wrote:
Hannu Krosing ha...@2ndquadrant.com writes:
On Thu, 2009-09-10 at 15:06 -0400, Robert Haas wrote:
It might
the underlying problem, just may make it
easier to understand and remember for users.
ANY [TYPE] and SAME AS [TYPE OF] are syntactic sugar indeed, but they
are much more SQL-like than needing to write any or anyelement(n) as
argument type or return type
--
Hannu Krosing http://www
in parentheses
Alvaro made
a good point about not wanting to multiply the various hard-wired
OID references, but perhaps some judicious code refactoring could
prevent a notational disaster.
regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL
(which is just list(anyelement)) and the need to list every type twice
in pg_type, once for the base type and once for the derived array
type.
/handwaving
...Robert
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
On Wed, 2009-09-09 at 21:57 +0200, Pavel Stehule wrote:
2009/9/9 Alvaro Herrera alvhe...@commandprompt.com:
Pavel Stehule escribió:
2009/9/9 Alvaro Herrera alvhe...@commandprompt.com:
I already published a pseudo-sprintf function in the wiki here:
a catch-all text or even text[] column at as the
last one of the table and gather all extra columns there ?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL
for it?
regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Thu, 2009-09-10 at 00:31 +0200, Dimitri Fontaine wrote:
Hi,
Tom Lane t...@sss.pgh.pa.us writes:
Hannu Krosing ha...@2ndquadrant.com writes:
anyelement(1), anyelement(2), ..., anyelement(N) and then match them by
the number in parentheses
Yeah, that idea occurred to me too
to be maintainable.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
would also make a lot of people very happy.
And we can also escape the need to uncompress TOAST'ed fields - just
markup the compression as another \c at the beginning of data.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting
, \n and \\
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a COMMIT; somewhere ? ;)
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
with 2-3X tolerance - to catch
most obvious regressions ?
regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
suggestion.
Have you been able to measure any speed difference between
--enable-selinux on and off ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
separately maintained release for a version or two, so
that we will have both PostgreSQL and SE-PostgreSQL and thus have an
easy way to compare both correctness and performance ?
Anyone remember how did Linux implement/introduce SE Linux ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL
does the right thing, especially when that
is so ill-defined in the case of fragments.
Is it just that in you _can't_ use Xpath on fragments, and you _need_ to
pass full documents to Xpath ?
At least this is my reading of Xpath standard.
cheers
andrew
--
Hannu Krosing http://www
On Mon, 2009-03-02 at 15:25 +0200, Peter Eisentraut wrote:
Hannu Krosing wrote:
Is it just that in you _can't_ use Xpath on fragments, and you _need_ to
pass full documents to Xpath ?
At least this is my reading of Xpath standard.
It is easy to read the XPath standard that way
On Sun, 2009-03-01 at 10:13 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Some of the functions, including some specified in the standard, produce
fragments. That's why we have the 'IS DOCUMENT' test.
But then you could use xmlfragments as the functions return type
On Fri, 2009-02-27 at 22:55 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Some of the functions, including some specified in the standard, produce
fragments. That's why we have the 'IS DOCUMENT' test.
But then you could use xmlfragments as the functions return
accepts me, start replicationg
So there could be several slaves, of both hot standby postgresql,
wal-file-store and store-and-forward-to-many types.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers
On Fri, 2009-02-27 at 12:21 -0800, Joshua D. Drake wrote:
On Fri, 2009-02-27 at 22:17 +0200, Hannu Krosing wrote:
Well VLDB is like 2% of what we need. If the above will remove all the
B.S. currently associated with actually doing PITR (rsync, scp, nfs,
pg_standby pick your poison
xmldocument and xmlforest/xmlfragments
types in next releases and leave the base xml as it is but deprecated
due to inability to fix it without breaking backwards compatibility.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
On Fri, 2009-02-27 at 16:37 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
On Thu, 2009-02-26 at 13:51 -0500, Robert Haas wrote:
What I have proposed for 8.3 should not break a single case that currently
behaves usefully. If anyone has a counter-example please show it.
What I
respectively.
Sincerely,
Joshua D. Drake
--
PostgreSQL - XMPP: jdr...@jabber.postgresql.org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
--
--
Hannu
On Tue, 2009-02-03 at 08:40 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Actually we came up with a solution to this - use filesystem level
snapshots (like LVM2+XFS or ZFS), and redirect backends with
long-running queries to use fs snapshot mounted to a different
mountpoint.
I
cache if needed) so the only bookkeeping you
need is which fs snapshots you need to keep and which can be released.
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent
On Tue, 2009-02-03 at 13:50 +, Gregory Stark wrote:
Hannu Krosing ha...@krosing.net writes:
Actually we came up with a solution to this - use filesystem level
snapshots (like LVM2+XFS or ZFS), and redirect backends with
long-running queries to use fs snapshot mounted to a different
On Tue, 2009-02-03 at 10:19 -0500, Robert Haas wrote:
On Tue, Feb 3, 2009 at 9:40 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Tue, 2009-02-03 at 09:14 -0500, Robert Haas wrote:
I think _the_ solution is to notice when you're about to vacuum a page
that is still visible to a running
On Tue, 2009-02-03 at 14:28 +, Simon Riggs wrote:
On Tue, 2009-02-03 at 08:40 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
Actually we came up with a solution to this - use filesystem level
snapshots (like LVM2+XFS or ZFS), and redirect backends with
long-running queries
On Wed, 2009-01-28 at 22:19 +0200, Heikki Linnakangas wrote:
Tom Lane wrote:
...
Well, those unexpectedly cancelled queries could have represented
critical functionality too. I think this argument calls the entire
approach into question. If there is no safe setting for the parameter
.
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
;)
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On Thu, 2009-01-08 at 18:02 -0500, Aidan Van Dyk wrote:
* Bruce Momjian br...@momjian.us [090108 16:43]:
The attached patch from Aidan Van Dyk zeros out the end of WAL files to
improve their compressibility. (The patch was originally sent to
'general' which explains why it was lost until
On Fri, 2009-01-09 at 01:29 +0200, Hannu Krosing wrote:
On Thu, 2009-01-08 at 18:02 -0500, Aidan Van Dyk wrote:
...
There's possible a few other ways to do it, such as zero the WAL on
recycling (but not fsyncing it), and hopefully most of the zero's get
trickled out by the OS before
On Mon, 2008-12-29 at 13:02 +0200, Heikki Linnakangas wrote:
That will ensure that the standby doesn't need to stall WAL
application because of read-only queries.
It doesn't need to. That is already optional.
Oh right. I should've added, without having to kill queries.
Even killing
On Wed, 2008-12-17 at 19:03 -0800, Unicron wrote:
I created a function for testing the patch, but when i run following
command, the function always raise an exception
select test_in_params('first');
ERROR: plpython: function test_in_params failed
DETAIL: exceptions.NameError: global name
synchronous replication on
basis that WAL Streaming - Synchronous Write is the highest security
level achievable using the feature.
And maybe have Sync Hot Standby as a feature on top of that which
provides WAL Streaming - Synchronous Apply
--
Hannu Krosing
On Sat, 2008-12-13 at 21:35 +0200, Hannu Krosing wrote:
We still could call Sync Rep as a feature synchronous replication on
basis that WAL Streaming - Synchronous Write is the highest security
level achievable using the feature.
And maybe have Sync Hot Standby as a feature on top
On Thu, 2008-12-11 at 15:20 +0200, Dmitry Turin wrote:
Hi, Pavel.
you have to show some real product, real project
Money will not be confirmed, until size of it will be known.
No IT solution can be confirmed or not, but business solution.
Budget for implementation is part of business
On Thu, 2008-12-11 at 16:48 +0100, Pavel Stehule wrote:
2008/12/11 Hannu Krosing [EMAIL PROTECTED]:
On Thu, 2008-12-11 at 15:20 +0200, Dmitry Turin wrote:
Hi, Pavel.
you have to show some real product, real project
Money will not be confirmed, until size of it will be known
On Sat, 2008-12-06 at 13:30 -0500, Andrew Chernow wrote:
Grzegorz Jaskiewicz wrote:
On 2008-12-06, at 18:21, Andrew Chernow wrote:
Looking for a way to limited a user to a specific set of queries. I
don't think this can be done right now ... or can it? Has this
feature request
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sun, 2008-11-16 at 23:20 +0300, Oleg Serov wrote:
Wee need to use shared memory for passing one BIGINT value(is session
throwout triggers), can you advice the method to get/set it with best
performance ?
have you tried setval(seq, value) to set and select last_value from
seq to read it.
or
On Mon, 2008-11-17 at 12:37 -0500, Andrew Dunstan wrote:
Hannu Krosing wrote:
On Sun, 2008-11-16 at 23:20 +0300, Oleg Serov wrote:
Wee need to use shared memory for passing one BIGINT value(is session
throwout triggers), can you advice the method to get/set it with best
performance
status in MySQL to find which mutex
is hot. But i don't know in PostgreSQL.
look at pg_locks system view
--
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
--
Sent via pgsql
On Tue, 2008-11-04 at 09:57 -0500, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
... even the code currently in CVS crashes the backend for this
py=# create or replace function add_any(in i1 anyelement, in i2
anyelement, out t text) language plpythonu as $$
return i1 + i2
On Tue, 2008-11-04 at 14:05 -0500, David Blewett wrote:
On Sat, Nov 1, 2008 at 7:52 AM, Hannu Krosing [EMAIL PROTECTED] wrote:
On Sat, 2008-11-01 at 06:13 +0200, Hannu Krosing wrote:
attached is a patch which enables plpython to recognize function with
multiple OUT params as returning
401 - 500 of 1744 matches
Mail list logo
