od for indexing hypothetical data ;-)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ing Bruce, but I fear this
is one itch that'll go unscratched.
Rest assured I'm not about to storm off and replace all my installations
with MySQL :-)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
turns out
better than the specific plan (due to bad stats or config settings or
just planner limitations). The question is (I guess): How many more
winners will there be than losers?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On 09/02/10 14:25, Jeroen Vermeulen wrote:
Richard Huxton wrote:
= Actual-cost threshold =
Also stop using the generic plan if the statement takes a long time to
run in practice.
Do you mean:
1. Rollback the current query and start again
2. Mark the plan as a bad one and plan again next
struck me:
1. Why have a separate recovery.conf file rather than just put the
commands inline? We can use the include directive to have them in a
separate file if required.
2. Why have a finish.replication file, rather than "SELECT
pg_finish_replication()"?
--
Richard Huxton
Archon
;
$foo1 = $seq_fn->($seq1);
$foo2 = $seq_fn->($seq2);
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 15/02/10 10:32, Tim Bunce wrote:
On Mon, Feb 15, 2010 at 07:31:14AM +, Richard Huxton wrote:
Is there any value in having a two-stage interface?
$seq_fn = get_call('nextval(regclass)');
$foo1 = $seq_fn->($seq1);
$foo2 = $seq_fn->($seq2);
t about what's going on?
SEARCHPATH->function()
SCHEMA('public')->function2()
Or did "SP" mean "Stored Procedure"?
On a (kind of) related note, it might be worthwhile to mention
search_path in the docs and point out it has the same pros/cons as unix
file pa
On 16/02/10 17:51, David E. Wheeler wrote:
On Feb 16, 2010, at 9:43 AM, Richard Huxton wrote:
Perhaps it would be better to be explicit about what's going on?
SEARCHPATH->function()
SCHEMA('public')->function2()
Or did "SP" mean "Stored Procedure"
- not sure
those carry any extra info. It also treads on the toes of
"PG->not_a_function" should such a beast be needed.
I like "F->funcname" or "FN->funcname" myself.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@po
nstall the adminpack etc. over the top of your now working installation.
If you didn't find the data directory, create it, grant permissions to
"postgres" and then try a full re-install.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgr
CT;
CREATE FUNCTION add_one(integer) RETURNS integer
AS 'My::Package', 'add_one'
LANGUAGE plperl STRICT;
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
unction "add_one_e"
-- plperlu - TestModule::add_one
richardh=# SELECT add_one_u(1);
add_one_u
---
2
(1 row)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 25/02/10 17:10, Andrew Dunstan wrote:
Richard Huxton wrote:
Presumably "Safe" just clamps down and my
sub isn't marked as acceptable. Is this intended, or am I doing
something stupid?
It's intended (at least by me).
Also, please see the recent discussion about load
ably meaning we need *another* config setting to prevent excessive
bloat on a heavily updated table on the master.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
x27;s hard to do, but that would really be
the most robust fix possible.
Something like snapshotting a filesystem, so updates continue while
you're still looking at a static version.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
On 26/02/10 14:45, Heikki Linnakangas wrote:
Richard Huxton wrote:
On 26/02/10 08:33, Greg Smith wrote:
I'm not sure what you might be expecting from the above combination, but
what actually happens is that many of the SELECT statements on the table
*that isn't even being updated* ar
queued WAL
before letting new transactions start. Or perhaps it replays any vacuum
activity it comes across and then stops. That should sync with #2
assuming the slave doesn't lag the master too much.
5. I've been mixing "defer" and "delay", as do the docs. We should
g system rather than a new app I'm pretty sure it would have
confused me for a lot longer than it did.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
configuration-for-extension. It allows the extension to decide whether
to load the new config or reject it. It lets you test/demonstrate
multiple configurations fairly simply.
The "system_data" column scenario can then be a default implementation
of read_your_config().
--
Richard Huxton
Ar
p can no longer
restore the oldest record :-(
IMHO The real solution would be something that could strip/rewrite the
constraint on restore rather than trying to prevent people being stupid
though. People *will* just tag their functions as immutable to get them
to work.
--
Richard Huxton
On 30/06/10 18:11, Magnus Hagander wrote:
On Wed, Jun 30, 2010 at 18:33, Richard Huxton wrote:
IMHO The real solution would be something that could strip/rewrite the
constraint on restore rather than trying to prevent people being stupid
though. People *will* just tag their functions as
e alpha testing
cycles on it."
Should we do this? Patch attached.
Any reason not to add a line to the 9.0 docs/release notes saying
"WARNING: The PGDG currently plan to change this setting's default in 9.1"?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers m
Trying to format the data in the backend is probably just going to
frustrate writers of different clients (of which I think we have quite a
few now).
* These functions could then be back-ported as an admin-pack too for
clients/apps that wanted cross-version compatibility for these sorts of
th
tgres from the existing psql
Arse.
It's little details like this that demonstrate why I'm a user and not a
hacker :-)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgres
olumns that get placed after the numeric. If you went from 10 bytes
down to 8, that should be visible.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
7;
COPY (SELECT :x) TO STDOUT;
-- Doesn't work
\copy (SELECT :x) TO '/tmp/test2.txt'
=== end script ===
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
=# select '1894-01-01'::timestamp with time zone;
timestamptz
--
1894-01-01 00:00:00-05:17:32
Floating-point timestamps? Although I thought integer was the default
for 9.x - hmm INSTALL says since 8.4
--
Richard Huxton
Archonet Ltd
--
Sent via pgs
"
password retrieved from file "/home/richardh/.pgpass"
I'm a bit puzzled how it manages without the escaping in the first case.
There's a lack of consistency though that either needs documenting or
fixing.
[1] http://www.postgresql.org/docs/9.1/static/libpq-
ms to
have noticed before now.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
eries-like function):
To support this I think we'd need to do something like:
create function mygs(int, int)
returns setof int
language plperl
with srfstate
as $$ ... $$;
Is this not what we do with aggregate functions at present?
--
Richard Huxton
Ar
think everyone can agree on. Being able to say that
values in different columns are related just gives the planner more
information to work with.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
end time spent waiting to commit".
I don't know how simple it is to measure/estimate the time spent for "#
of transactions that finish while an fsync is taking place".
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
p not pick up a partially-written
page? Assuming it's being written to as the backup is in progress. (We
are talking about when disk blocks are smaller than PG blocks here, so
can't guarantee an atomic write for a PG block?)
--
Richard Huxton
Archonet Ltd
-
Simon Riggs wrote:
On Fri, 2007-03-30 at 11:27 +0100, Richard Huxton wrote:
Is that always true? Could the backup not pick up a partially-written
page? Assuming it's being written to as the backup is in progress. (We
are talking about when disk blocks are smaller than PG blocks her
ot; rather than "equal".
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
friend 4ever wrote:
Hi,
I am getting the parse error while i try to execute a simple sql query in postgres.
This isn't a question for the hackers list.
Try the general, or jdbc lists.
--
Richard Huxton
Archonet Ltd
---(end of broa
ickest way to find out what the error is would be to
provide the *actual* query, not something very much like it. Perhaps
turn statement logging on in your postgresql.conf if it isn't already.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)--
ey could play a part in foreign keys that would be useful too.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
with
re-checking clauses involving subqueries or joins I'd guess.
I'm trying to decide if it's unexpected or just plain wrong, and I think
I'd have to argue wrong.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP
Richard Huxton wrote:
Heikki Linnakangas wrote:
The problem is that the new tuple version is checked only against the
condition in the update rule, id=OLD.id, but not the condition in the
original update-claus, dt='a'.
Yeah, that's confusing :(.
Bit more than just normal rul
Hiroshi Inoue wrote:
Richard Huxton wrote:
Heikki Linnakangas wrote:
The problem is that the new tuple version is checked only against the
condition in the update rule, id=OLD.id, but not the condition in the
original update-claus, dt='a'.
Yeah, that's confusing :(.
Bit
x27;m suspicious if UPDATABLE VIEWS can be implemented
using the rule system.
Remember this affects all self-referential joins on an UPDATE (and
DELETE?) not just views. It's just that a rule is more likely to produce
that type of query.
--
Richard Huxton
Ar
don't claim to have looked at
it in detail it seems to pretty much do what it claims to.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Dave Page wrote:
Richard Huxton wrote:
Magnus Hagander wrote:
It's been on my list to rewrite the whole archive system for a while
for various reasons. There is quite a bit of crossover with the patch
tracker I proposed so I was hoping to look at both together.
Let me know when you sta
want to
decide how to handle the "inherits" flag.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
he
current role a member of role X rather than list all the roles that are
members of X.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
self-referential updates"
Hiroshi originally noted the problem in one of his views here:
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 9: In versions belo
( pg_cancel_backend() ).
For the rest, that's what ssh is for imho.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Zdenek Kotala wrote:
Richard Huxton wrote:
For the rest, that's what ssh is for imho.
And what you will do when you don't have ssh access on this machine and
5432 is only one way how to administrate a server? (Windows is another
story.)
If I've not got ssh access to the ma
Marcos FabrÃcio Corso wrote:
I would like to leave the list ...
Not really a question worth posting several lists. If you don't know how
to unsubscribe, try starting with the form linked from here.
http://www.postgresql.org/community/lists/
--
Richard Huxton
Archone
1BC and 1AD).
Presumably this can only happen if using floating-point datetimes and
not 64-bit integers?
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
binary data types
in libpq.
Um - speaking as a user, not a developer, I don't actually see a
description of what problem(s) you are suggesting be solved. Are you
saying there should be better documentation, or a new format?
--
Richard Huxton
Archonet Ltd
---(e
re in making
changes. However, I've seen a lot of changes come and go and I think
you'll need to make progress on those 4 points to get anywhere.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
er possibility: "synchronous_commit = off"
Ooo, I like that. Any other takers?
I like "synchronous_commit = off", it even has a little girlfriend
getting spin while being accurate :)
Or perhaps "sync_on_commit = off"?
Less girlfriend-spe
thing else?)*
It's obvious to people on the -hackers list what we're talking about,
but is it so clear to a newbie, perhaps non-English speaker?
* I can see people thinking this means something like "commit_delay".
--
Richard Huxton
Archonet Ltd
--
auditing what features are in use (or
have changed between versions).
Or are these examples of changes that will only be allowed e.g. every
other major version.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 3: Have you checked our
tgreSQL itself. This question is better suited to the
general / sql / admin lists perhaps.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
at function compile-time
that doesn't seem much better.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
amiliar with the terms you're using.
- Database independence
In particular, this one makes no sense to me.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
n is defined "STRICT"? That should
automatically return null if a parameter is null without calling the
function.
Simplest way to check is probably to pg_dump --schema-only and search
for the function defn.
--
Richard Huxton
Archonet Ltd
--
Hmm - tricky bit would presumably be the logging statement itself. Would
it be possible to keep the overheads low enough without interfering with
plpgsql itself?
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
le since the
profiler is doing that. Also, I'm not thinking of this as a way of
logging things permanently, just for debugging purposes.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
n comment them out when not testing. Perhaps I'm optimising
prematurely though. I'll have to run some timing tests...
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
?
Well it's unlikely to be "real soon" since 8.3 is currently approaching
beta-test.
Surely memcached+pgmemcache does basically this anyway, except:
- it's not restricted to function outputs
- you can cache application objects
- you can spread your cache across multiple ma
es.
http://www.postgresql.org/docs/8.2/static/warm-standby.html
Particularly section 23.4.4
That can get you to 1 second or less.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
Value for WAL
Files is 16 MBytes).
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 3
o copy individual disk blocks between machines.
You could do this just for WAL.
3. Replication.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
detecting the existence of a JRE.
Can help here:
http://pgfoundry.org/projects/pginstaller/
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
... AS ON INSERT ... DO INSTEAD SELECT f(NEW.test1);
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
QUE constraints"
If you can program in "C" or can fund someone who can, I'm sure people
would like to see it fixed for version 8.4. Don't underestimate the work
involved though.
HTH
--
Richard Huxton
Archonet Ltd
---(end of broadcast)
2.sql install script you can change the
schema it installs to. That should make it easier to identify everything
it installs.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desi
to show the first set of records. It takes a long time, even
to quit after i pressed 'q'.
With oracle SQLPlus, it is quite instantaneous.
Again, you're measuring different things. What is the time to the *last*
row?
--
Richard Huxton
Archonet Ltd
--
see you've checked and seen it does work. I'm not a java man, but I do
know there are ways to control this. Perhaps try the -jdbc mailing list.
In any case, I think we've established it's nothing for the hackers list.
--
Richard Huxton
Archonet Ltd
---
Trevor Talbot wrote:
On 11/12/07, Richard Huxton <[EMAIL PROTECTED]> wrote:
Gokulakannan Somasundaram wrote:
I also noticed that it doesn't crash with psql, but it takes a
long time to show the first set of records. It takes a long time, even
to quit after i pressed 'q&
ning.
Traditionally I think the extras stuff for PG packages has been /contrib
but obviously that's not a strict rule.
* PS - it's a useful feature - good work to all concerned*
** PPS - 8.3 is looking good too. This short development cycle is
working wonders ;-)
--
ever, they seem a lot "heavier" than a dictionary file and
it seems less likely an admin (e.g. me) might fail to prepare the target
accordingly.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help suppo
it of flagging rather than file-segments. That obviously complicates
the tracking but means you can cope with infrequent updates as well as
mark most of the "most recent" segment for log-style tables.
--
Richard Huxton
Archonet Ltd
---(e
Simon Riggs wrote:
On Fri, 2008-01-04 at 10:22 +, Richard Huxton wrote:
Simon Riggs wrote:
We would keep a dynamic visibility map at *segment* level, showing which
segments have all rows as 100% visible. No freespace map data would be
held at this level.
Small dumb-user question.
I take
ages ago to do this sort of thing. Hopefully that will help you.
--
Richard Huxton
Archonet Ltd
-- History Tracking Trigger-Functions
--
BEGIN;
-- tcl_track_history(TABLE-NAME)
-- Set TABLE-NAME when creating the trigger. Will automatically record change
-- details in tables history/history
rth of
blocks wasted per partition) and allow for stretchy partitions at the
cost of an extra layer of indirection.
For the single-partition case you'd not need to split the file of
course, so it would end up looking much like the current arrangement.
--
Richard Huxton
Archonet
Csaba Nagy wrote:
On Fri, 2008-01-11 at 11:34 +, Richard Huxton wrote:
1. Make an on-disk "chunk" much smaller (e.g. 64MB). Each chunk is a
contigous range of blocks.
2. Make a table-partition (implied or explicit constraints) map to
multiple "chunks".
That would
Simon Riggs wrote:
On Fri, 2008-01-11 at 11:34 +, Richard Huxton wrote:
Is the following basically the same as option #3 (multiple RelFileNodes)?
1. Make an on-disk "chunk" much smaller (e.g. 64MB). Each chunk is a
contigous range of blocks.
2. Make a table-partition (implied o
omething like:
pg_dump -l mydb | grep BEFORE > obj_list.txt
pg_dump -L obj_list.txt mydb > mydb.before.schema
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
ttribute_as_text(NEW, 'id') or even
get_attribute_quoted(NEW, 'id')
It would be nice to have a more dynamic language built-in. I'm not aware
of any BSD-licensed dynamic languages though.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)-
writing out the hint bits to disk anyway? Is it really so
slow to calculate them on read + cache them that it's worth all this
trouble? Are they not also to blame for the "write my import data twice"
feature?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing
Greg Stark wrote:
> On Tue, Dec 1, 2009 at 9:57 PM, Richard Huxton wrote:
>> Why are we writing out the hint bits to disk anyway? Is it really so
>> slow to calculate them on read + cache them that it's worth all this
>> trouble? Are they not also to blame for the &
be
Wait for it
9.0.
You don't have a code-name. All the cool kids have code-names for their
projects.
There - that should distract everyone from actual release-related work
for the next week or so :-)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (
one go to see an example of a problem.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
both groups and can only be vacuumed based on
T0..Tn (presumably T0 is the oldest, since that's the point of the
exercise).
An attempt to write to user_emails by T0 will fail with an error.
An attempt to read from user_emails by T0 will be allowed?
What happens if I'm in ISOLATION L
Simon Riggs wrote:
On Thu, 2008-08-07 at 14:18 +0100, Richard Huxton wrote:
An attempt to write to user_emails by T0 will fail with an error.
All above correct
The point of doing this is that *if* T0 becomes the oldest transaction
it will *not* interfere with removal of rows on "user_e
orry whether applications might be affected by an incompatible change.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
7;s only one value here: "hot standby wal delay time before
cancelling query". Might be a shorter name.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
he
impact of all the options where the accessed tables weren't being
updated (where update = vacuum + HOT if I've got this straight).
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
an and restart then we could just try the
quick-but-risky plan and if we reach 50 rows rather than the expected 10
try a different approach. That way we'd not need to gather stats, just
react to the situation in individual queries.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
st executing the planner-node at this
point? You could scale with the cost of actually doing the tests.
> 3. Put in a narrow hack that will get us out of this specific case,
> but might still allow very slow proof attempts in other large cases.
>
> The specific narrow hack I'm cons
t thinks this should be a service on the website too
(or even first)? Fill in web form, click button, get sample
postgresql.conf (with comments) back.
Add a tick-box asking if we can keep a copy of their answers and you
might get some useful usage info too.
--
Richard Huxton
Archonet Ltd
--
Sent
ble and I haven't missed something - I'm still
> learning!
Have you considered restoring to a completely different database
(report1/report2) and just switching between them?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To ma
tart, txid_end,
time_end, length? Write it once when you start using the file and once
when it's finished.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Aidan Van Dyk wrote:
> * Richard Huxton [090109 12:22]:
>
>>> Yeah: the archiver process doesn't have that information available.
>
>> Am I being really dim here - why isn't the first record in the WAL file
>> a fixed-length record containing e.g. txid_
1 - 100 of 353 matches
Mail list logo
