,
Dawid
--
..``The essence of real creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting from idea to idea
: qne...@gmail.com : without getting bogged down by fixated demands.''
`..' Sherkaner Underhill, A Deepness in the Sky, V
,
Dawid
--
..``The essence of real creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting from idea to idea
: qne...@gmail.com : without getting bogged down by fixated demands.''
`..' Sherkaner Underhill, A Deepness
should be better.
My question is: does it look like a good TODO item? :)
Best regards,
Dawid
--
..``The essence of real creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting from idea to idea
: qne...@gmail.com : without getting
partitioning it leads
to confusion (parent table was not updated, but the child table is
(or isn't because there were really 0 rows updated -- you can't really tell)).
Best regards,
Dawid
--
..``The essence of real creativity is a certain
: *Dawid Kuroczko
enough to know how that would work in encodings like UTF16...
See http://doxygen.postgresql.org/encode_8c-source.html#l00107
Best regards,
Dawid Kuroczko
--
..``The essence of real creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting
. during recovery database replay all WAL-logged pages. The X page
was not WAL-logged, thus it is not replayed.
3. when replaying is finished, everything looks OK at this point
4. user runs a SELECT which hits page X. Oops, we have a checksum
mismatch.
Best regards,
Dawid Kuroczko
we know which bit to flip
and that we accept the check will be a bit
weaker. :) OTOH this shouldn't happen too
often, so performance should matter much.
My 0.02
Best regards,
Dawid Kuroczko
[1]: Of course it would be more efficient to flip
the checksum, but it would be tricky
creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting from idea to idea
: [EMAIL PROTECTED] : without getting bogged down by fixated demands.''
`..' Sherkaner Underhill, A Deepness in the Sky, V. Vinge
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Hello!
Currently the TOASTing code does its magic when whole tuple is
larger than TOAST_TUPLE_TARGET which happens to be around 2KB.
There are times though when one is willing to trade using (fast) CPU to
reduce amount of (slow) I/O. A data warehousing types of workload
most notably. Rarely
On Tue, Jun 10, 2008 at 5:25 PM, Tom Lane [EMAIL PROTECTED] wrote:
Dawid Kuroczko [EMAIL PROTECTED] writes:
As we already have four types of ALTER COLUMN .. SET STORAGE
{ PLAIN | EXTERNAL | EXTENDED | MAIN } I would like to add
COMPRESSED which would force column compression (if column
On Wed, May 7, 2008 at 7:52 AM, KaiGai Kohei [EMAIL PROTECTED] wrote:
Tom, Thanks for your reviewing.
The patch hasn't got a mode in which SELinux support is compiled in but
not active. This is a good way to ensure that no one will ever ship
standard RPMs with the feature compiled in, because
On Thu, May 29, 2008 at 4:12 PM, Tom Lane [EMAIL PROTECTED] wrote:
The Postgres core team met at PGCon to discuss a few issues, the largest
of which is the need for simple, built-in replication for PostgreSQL.
[...]
We believe that the most appropriate base technology for this is
1 probably
On Mon, Apr 14, 2008 at 5:01 PM, Csaba Nagy [EMAIL PROTECTED] wrote:
On Mon, 2008-04-14 at 10:55 -0400, Mark Mielke wrote:
The other ideas about automatically deciding between plans based on
ranges and such strike me as involving enough complexity and logic, that
to do properly, it might
On Mon, Apr 14, 2008 at 6:45 PM, Alvaro Herrera
[EMAIL PROTECTED] wrote:
[...]
As far as the Wiki page is concerned, it would be good to make sure the
entries have a bit more info than just a header line -- things such as
author, who reviewed and what did the reviewer say about it.
Some
On Sun, Apr 13, 2008 at 2:26 PM, PFC [EMAIL PROTECTED] wrote:
Oracle keeps a statement/plan cache in its shared memory segment (SGA)
that greatly improves its performance at running queries that don't
change very often.
Can we have more details on how Oracle does it ? For
On Sat, Apr 12, 2008 at 2:44 PM, Perez [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED],
PFC wrote:
So, where to go from that ? I don't see a way to implement this
without
a (backwards-compatible) change to the wire protocol, because the clients
will want to specify
On Thu, Apr 3, 2008 at 6:44 PM, Alvaro Herrera
[EMAIL PROTECTED] wrote:
Bruce Momjian escribió:
It seems more helpful if there were \x option to use extended format
only when the output is too wide. TODO already has:
o Add auto-expanded mode so expanded output is used if
Hi!
I have sent a patch to pgsql-patches:
http://archives.postgresql.org/pgsql-patches/2008-04/msg00050.php
...which adds \G command to psql client.
The idea of \G command is to perform the query, but with printing
query results using extended table output format.
For example:
postgres=#
On Thu, Apr 3, 2008 at 4:35 PM, Tom Lane [EMAIL PROTECTED] wrote:
Dawid Kuroczko [EMAIL PROTECTED] writes:
The idea of \G command is to perform the query, but with printing
query results using extended table output format.
Seems a bit useless --- if you prefer \x format, wouldn't you
On Thu, Mar 20, 2008 at 4:56 PM, Decibel! [EMAIL PROTECTED] wrote:
This would be very useful for me, and would satisfy the OP's request.
Can we get a TODO?
If you feel adventureous you may UPDATE catalog constrains directly,
which will work more or less as enforce, don't validate, don't lock.
On Mon, Mar 17, 2008 at 6:23 PM, Tom Lane [EMAIL PROTECTED] wrote:
I'm not wedded to forks, that's just the name that was used in the
only previous example I've seen. Classic Mac had a resource fork
and a data fork within each file.
Don't think I like maps though, as (a) that prejudges
On Fri, Mar 7, 2008 at 3:51 PM, Bruce Momjian [EMAIL PROTECTED] wrote:
~ Jim C. Nasby wrote:
On Wed, Jul 04, 2007 at 01:03:20PM +0200, Dawid Kuroczko wrote:
Hello.
I think it could be a nice idea to put descriptions from
http://www.postgresql.org/docs/8.2/static/catalogs.html
On Sun, Mar 9, 2008 at 7:25 PM, Tom Lane [EMAIL PROTECTED] wrote:
=?ISO-8859-2?Q?Micha=B3_Zaborowski?= [EMAIL PROTECTED] writes:
I would like to be able to add CONSTRAINT and/or DEFAULT with out
affecting old rows.
You mean without actually checking that the old rows satisfy the
Following the discussion on making UUID data type to be much more liberal
( http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php )
I have decided to try to approach it from more general perspective.
The current state of code is available at:
On Thu, Feb 28, 2008 at 11:27 AM, Albe Laurenz [EMAIL PROTECTED] wrote:
The LDAP case is the main motivation why I would like to have
wildcards, so that all our databases could be handled with one
entry in the service file. Currently we have to add an entry to the
file for every new
Hello.
I am currently playing with UUID data type and try to use it to store provided
by third party (Hewlett-Packard) application. The problem is they
format UUIDs as
-------, so I have to
replace(text,'-','')::uuid for
this kind of data.
Nooow, the case is
On Feb 19, 2008 10:31 PM, Josh Berkus [EMAIL PROTECTED] wrote:
Magnus, All,
This is something I've been thinking about too, just because my efforts to
write auto-config scripts have gotten bogged down in the need to parse and
write .conf files in a paltform-agnostic way and preserve comments.
On Feb 19, 2008 8:31 AM, ITAGAKI Takahiro
[EMAIL PROTECTED] wrote:
Tom Lane [EMAIL PROTECTED] wrote:
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
In my workload, ANALYZE takes long time (1min at statistics_target = 10,
and 5min at 100), but the updated table needs to be vacuumed every 30
On Wed, Feb 20, 2008 at 7:34 PM, Tom Lane [EMAIL PROTECTED] wrote:
Josh Berkus [EMAIL PROTECTED] writes:
2) allow *commenting* of pg_settings / SET PERMANENT. Thus:
SET PERMANENT work_mem = '12mb' COMMENT '16mb too high; OOM';
Ugh :-(
I think that putting this into SET is a pretty
On Thu, Feb 21, 2008 at 12:02 AM, Josh Berkus [EMAIL PROTECTED] wrote:
All,
I think we're failing to discuss the primary use-case for this, which
is one reason why the solutions aren't obvious.
And that use case is: multi-server management.
...and third-party management solutions.
On Feb 7, 2008 11:59 PM, Martijn van Oosterhout [EMAIL PROTECTED] wrote:
On Thu, Feb 07, 2008 at 08:22:42PM +0100, Dawid Kuroczko wrote:
Nw, I know work_mem is not total per process limit, but
rather per sort/hash/etc operation. I know the scheme is a bit
sketchy, but I think
On Feb 5, 2008 10:54 PM, Ron Mayer [EMAIL PROTECTED] wrote:
Decibel! wrote:
Yes, this problem goes way beyond OOM. Just try and configure
work_memory aggressively on a server that might see 50 database
connections, and do it in such a way that you won't swap. Good luck.
That sounds like
On 8/27/07, Albe Laurenz [EMAIL PROTECTED] wrote:
Dawid Kuroczko wrote:
Then again, apart from libpq I don't see it mentioned anywhere.
[...]
Looking at the 8.3devel documentation...
I think it should be mentioned in 18. Server Configuration. probably
somewhere in 18.3 Connections
On 8/14/07, Chris Browne [EMAIL PROTECTED] wrote:
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective implementations,
seeing some similarities and
On 7/31/07, Devrim GÜNDÜZ [EMAIL PROTECTED] wrote:
Hi,
On Mon, 2007-07-30 at 19:14 -0700, Joshua D. Drake wrote:
and RHEL performed much better than CentOS.
Not to be unkind, but I doubt that on an identical configuration.
Since I don't have the permission to distribute the benchmark
On 7/25/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Why? What are you trying to achieve?
I am implementing a technique that sorts a result set according to weight
annotations in the WHERE.
The query
SELECT * FROM cars
WHERE (cdChanger=1){2}
OR (mp3player=1){1}
would be sorted
Hello.
I think it could be a nice idea to put descriptions from
http://www.postgresql.org/docs/8.2/static/catalogs.html
into system catalogs itself. I.e., make a bunch of
COMMENT ON COLUMN pg_class.relname
IS 'Name of the table, index, view, etc.';
...
COMMENT ON COLUMN pg_class.relkind
Hello, I have a system where there are mostly COPYs,
which insert data into a table. Ocasionally a COPY will fail (and thus,
dead rows appear), but as far as I can tell ROLLBACK is not reflected
anywhere in the pg_stats_user_tables. And since there are no rows
n_tup_upd or n_tup_del, therefore
On 4/28/07, Simon Riggs [EMAIL PROTECTED] wrote:
I think the community has to come up with ideas on how to accomplish this.
My thinking is to move to a two stage release process: Do one
production release annually, and one dev release at the 6 month
mid-point. That way each new release contains
On 3/15/07, Grzegorz Jaskiewicz [EMAIL PROTECTED] wrote:
I figure - I should start brand new thread for this one - so here you
go.
I am in a need for verbose CLUSTER. Ie. one that would give me
feedback and progress.
Because CLUSTER is divided into two major operations, (data
reordering, index
On 2/17/07, Tom Lane [EMAIL PROTECTED] wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
How easy/hard would it be to create unique indexes on tinterval (unique
here meaning non-overlapping) ?
Overlapping is not an equality relation (it fails the transitive law),
so I'm not entirely sure what
On 1/24/07, Andrew Dunstan [EMAIL PROTECTED] wrote:
Peter Eisentraut wrote:
contrib is a horrible misnomer. Can we maybe bite the bullet and call
it something else?
plugins?
How about 'modules' or 'extras' or 'extensions'? :)
standard-plugins might be more informative. I think of them as
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
anything that doesn't appear to me to be handled by
the disaster
recoverer should leave a detailed log which would be enough to
detect software-corruption even after the recovery [and users should
be advised to send them].
Regards,
Dawid Kuroczko
---(end of broadcast)---
TIP 9: In versions
On 10/25/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Joshua D. Drake wrote:
Bruce Momjian wrote:
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
I think this is a good reason not to list *any* of the products by name
in the documentation, but instead refer to a page on say
On 10/23/06, Tom Lane [EMAIL PROTECTED] wrote:
It's not so much that I don't trust Intel as that a CRC algorithm is
exactly the sort of nice little self-contained thing that people love
to try to patent these days. What I am really afraid of is that someone
else has already invented this same
Recently I've been playing with quite a big table (over 50mln rows),
and did some SELECT ... sum(...) WHERE ... GROUP BY ... queries.
The usual plan for these is to sort the entries according to GROUP BY
specification, then to run aggregates one by one. If the data to be
sorted is large enough,
On 9/14/06, Gevik Babakhani [EMAIL PROTECTED] wrote:
At this moment we (almost) have a uuid/guid datatype.
As suggested in earlier discussion we provide a raw/plain output of the
uuid type:
devdb=# select * from tbluuid;
pk|
--+
There is a well known command called CLUSTER which organizes tablein specified index's order. It has a drawback, that new tuples added arenot in this order. Last night I had idea which could be interesting, I hope.
The idea is to make use of 'histogram_bounds' collected statistical data.Instead of
On 5/22/06, Martijn van Oosterhout kleptog@svana.org wrote:
On Mon, May 22, 2006 at 10:00:22AM -0500, Jim C. Nasby wrote:
T-SQL has statement-level triggers, and they get used a lot (some big apps
ONLY put code in triggers). Statement-level triggers are very efficient for
maintaining
On 5/22/06, Mark Woodward [EMAIL PROTECTED] wrote:
Except that apt doesn't work on all platforms. Though it would certainly
make sense to look at lifting the framework for CPgAN from somewhere,
rather than coding it ourselves.
A CPgAN would be a great idea in theory, but I have reservations.
On 5/20/06, Lukas Smith [EMAIL PROTECTED] wrote:
The improvements to the installer are great, but there simply needs to
be a packaged solution that adds more of the things people are very
likely to use. From my understanding Bizgres goes in that direction? I
just think that whatever highly
On 5/9/06, PFC [EMAIL PROTECTED] wrote:
You might consider just selecting your primary key or a set of
primary keys to involved relations in your search query. If you
currently use select * this can make your result set very large.
Copying all the result set to the temp. costs you
On 5/1/06, Martijn van Oosterhout kleptog@svana.org wrote:
On Mon, May 01, 2006 at 01:19:30PM -0500, Jim C. Nasby wrote: ISTM that tying this directly to maintenance_work_mem is a bit confusing, since the idea is to keep vacuum transaction duration down so that it isn't causing dead tuples to
On 8/26/05, Alvaro Herrera [EMAIL PROTECTED] wrote:
Or, slightly different, what are people's most wanted features?
One feature, or rather set of features which was missing from the list and I think
it is important: i18n. :)
I mean, PostgreSQL has a number of good features concerning
On 13 Aug 2005 21:42:45 -0400, Greg Stark [EMAIL PROTECTED] wrote:
Tom Lane [EMAIL PROTECTED] writes:
However, if you favor a no thought required approach, listing 'em
all is certainly the path of least resistance. I'm just dubious that
that maximizes the usefulness of tab completion.
I'm
Hello. I was just wondering, assume we have such tables:
CREATE TABLE data (
foo text,
somename_id integer not null references (somenames)
);
CREATE TABLE somenames (
somename_id serial PRIMARY KEY
somename text NOT NULL
);
And a view:
CREATE someview AS SELECT foo,somename FROM
On 7/22/05, Tom Lane [EMAIL PROTECTED] wrote:
This is quite strange. The nestloop plan definitely should be preferred
in the context of the LIMIT, considering that it has far lower estimated
cost. And it is preferred in simple tests for me.
After a suitable period of contemplating my
On 7/21/05, Josh Berkus josh@agliodbs.com wrote:
Also, it would be a good time to suggest some way for making
EXPLAIN script-friendly. Like return data as a computer program
convenient table?
I'm already trying to kludge this in Perl. It would help automated testing
considerably if
On 7/20/05, Simon Riggs [EMAIL PROTECTED] wrote:
Since it's also possible to do partitioning with UNION ALL, maybe it
would be better if there was an option to explain that told it either to
show or not show info about eliminated partitions. That would seem to
serve the general case better
On 7/7/05, Bruce Momjian pgman@candle.pha.pa.us wrote:
One idea would be to just tie its behavior directly to fsync and remove
the option completely (that was the original TODO), or we can adjust it
so it doesn't have the same risks as fsync, or the same lack of failure
reporting as fsync.
I
On 7/3/05, Andreas Pflug [EMAIL PROTECTED] wrote:
Yup, attached. Per our earlier conversation, pg_dbfile_size() now
returns the size of a table or index, and pg_relation_size() returns the
total size of a relation and all associated indexes and toast tables
etc.
pg_relation_size's name
On 6/30/05, Dave Page dpage@vale-housing.co.uk wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I have a new idea
On 6/28/05, Martín Marqués martin@bugs.unl.edu.ar wrote:
El Mar 28 Jun 2005 13:58, PFC escribió:
Personnally I use one table which has columns (domain, name) and which
stores all enum values for all different enums.
I have then CHECK( is_in_domain( column, 'domain_name' )) which
On 6/1/05, Zeugswetter Andreas DAZ SD [EMAIL PROTECTED] wrote:
You could create a separate bufferpool per page size. Of course that
has other disadvantages.
Is it really so difficult to create and attach another shmem segment ?
Well, I don't think it is much different from having two
On 6/1/05, Hans-Jürgen Schönig [EMAIL PROTECTED] wrote:
Personally I don't think that it is a good idea to do that.
People will tend to corrupt their systems because they want speed
(sometimes without thinking about the consequences).
I can only think of one scenario where nologging would
On 5/6/05, Greg Sabino Mullane [EMAIL PROTECTED] wrote:
As long as they are in a separate schema (like information_schema,
but hopefully not as long). pg_views? pg_info? information_skema? :)
But if you think that nobody needs these views, it's because you
haven't had much contact with end
On 5/2/05, Heikki Linnakangas [EMAIL PROTECTED] wrote:
What we can do in PostgreSQL is to introduce an application-level
heartbeat. A simple Hello world message sent from server to client that
the client would ignore would do the trick.
Hmm, a quick-and-dirty implementation could be that a
On Wed, 2 Feb 2005 19:04:04 -0300, Alvaro Herrera
[EMAIL PROTECTED] wrote:
It is not pilot error if PostgreSQL allows it. There is
nothing illegal about the above commands in their execution.
The pg_dump application should recognize that the object has
changed and react accordingly.
On Sat, 29 Jan 2005 18:46:44 +, Mike Rylander [EMAIL PROTECTED] wrote:
As a side note, wouldn't the in-memory bitmaps pretty much kill the
need for multicolumn indexes? It seems that they would be able to
join index scans on the same table, and then there would be no need
for industrial
On Sat, 29 Jan 2005 21:54:39 +0200, Victor Yegorov [EMAIL PROTECTED] wrote:
* Dawid Kuroczko [EMAIL PROTECTED] [29.01.2005 21:25]:
With in-memory bitmap, the search would start with index a, all
matching rows would form the bitmap; then the second search
would go through b index, forming
On Sat, 22 Jan 2005 17:09:42 -0500, Tom Lane [EMAIL PROTECTED] wrote:
This time setlocale() was needed to get the behaviour
I needed (database initdb'ed to 'C', my order set to 'pl_PL',
or whatever locale I need at given moment).
I would imagine that the performance is spectacularly awful
On Tue, 18 Jan 2005 23:05:57 +0100, Reinoud van Leeuwen
[EMAIL PROTECTED] wrote:
Contrary to popular misconception, virtually all countries
grant software patents. The problem is that people have
Thanks to the new European Union member Poland, the Dutch plan to put the
software patents on
Hello!
One of least liked by me features of PostgreSQL is a need to specify
LC_CTYPE an LC_COLLATE at initdb time. Especially if you intend to
put into DB texts in
different languages (say, Polish, French, German and Russian) and use
functions like lower() or ORDER BY these texts. :)
I guess
On 15 Nov 2004 02:00:37 -0500, Greg Stark [EMAIL PROTECTED] wrote:
I think people should get away from thinking about order by + limit. That
isn't going to work for anything with a GROUP BY. And it isn't going to work
for anything more complex than a single min() or max().
min() only needs
Hello, recently I've been trying to write a plperlu function like this:
CREATE FUNCTION foo RETURNS bytea AS '
use Storable qw(freeze thaw);
my @a = (1,2,3,4,5);
return freeze ([EMAIL PROTECTED]);
' LANGUAGE plperlu;
In other words, serialize some data (maybe some rows, would be a great
76 matches
Mail list logo
