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
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
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-pgpass.html
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
=# 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 pgsql-hackers
) 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
-for-user from
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
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
this in
an existing 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
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
.
--
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
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.postgresql.org/mailpref
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 mailing list (pgsql-hackers
.
--
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
this stuff from ancient blog entries.
Understanding is not necessary. Hell, I do it sometimes if I'm dealing
with something like LDAP where I don't really have a deep knowledge of
the situation.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
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
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)
To make changes
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* are canceled
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
probably settle on one or the other. I think defer conveys the meaning
more precisely, but what about non-native English speakers?
--
Richard Huxton
Archonet
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 loading extra stuff
.
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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
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
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@postgresql.org)
To make changes to your subscription:
http
('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 paths.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers
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?
Yes.
Hmm - might be worth avoiding
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);
I don't think
);
$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
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
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
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 changes
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
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 (pgsql
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 list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Greg Stark wrote:
On Tue, Dec 1, 2009 at 9:57 PM, Richard Huxton d...@archonet.com 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 write my import data
be
considered an operator.
http://www.postgresql.org/docs/8.4/static/functions-comparisons.html#AEN16561
Got caught by the same thing a couple of days ago.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
at the
same time.
You're going to upset a lot of managers if they can't do that ;-)
--
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
string comparisons be safe (because a
literal would be caught before the view gets evaluated)?
--
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
, but solves the 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
;
$$ LANGUAGE plpgsql COST 999;
CREATE VIEW phone_number AS
SELECT person, phone FROM phone_data WHERE NOT row_hidden(phone);
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
;
^^^
This is the expression that needs to be expensive. Then the exposing
function needs to be cheap. That makes the planner run the exposing
function first.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Richard Huxton wrote:
Heikki Linnakangas wrote:
CREATE VIEW phone_number AS
SELECT person, phone FROM phone_data WHERE phone NOT LIKE '6%';
CREATE OR REPLACE FUNCTION expose_person (person text, phone text)
RETURNS bool AS $$
begin
RAISE NOTICE 'person: % number: %', person, phone
not bad result, but, yes, I see what I could not to see.
Ah - that's the problem. It's not possible to get the hidden values
into the result set, but it is possible to see them. It only matters if
you are using the view to prevent access to certain rows.
--
Richard Huxton
Archonet Ltd
Peter Eisentraut wrote:
On Fri, 2009-07-17 at 13:58 +0100, Richard Huxton wrote:
2. Titles on navigation links.
Run ./STYLING/title_links.pl and it should add title attributes to the
navigation links. This means hovering over the top links gives the title
of the page they will go
David E. Wheeler wrote:
On Sep 29, 2009, at 8:55 AM, Richard Huxton wrote:
For the browser, does the following match what you're after, Andrew?
- clicking chapter title opens the browser panel
- panel stays open until you click close icon
- panel contains collapsable tree of chapter/section
David E. Wheeler wrote:
On Oct 1, 2009, at 1:12 AM, Richard Huxton wrote:
Why wouldn't the entire TOC be in a collapsed list?
Permanently on-screen? My only concern there would be for people viewing
on phones etc.
I have to admit that I'm never looking at the Pg docs on my iPhone
, if we just reference it from
google?)
- navigation is optional, disabling js leaves docs as at present
- works on all reasonable browsers (anything not IE6)
- works online and in downloaded docs (except Windows .chm of course)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers
, echo boolean
) RETURNS text LANGUAGE plpgsql AS $exec$
Perhaps another two functions too:
list_all(objtype, schema_pattern, name_pattern)
exec_for(objtype, schema_pattern, name_pattern, sql_with_markers)
Obviously the third is a simple wrapper around the first two.
--
Richard Huxton
well
established.
I hope that provides some clarity.
It's useful to learn that `ROW(NULL, NULL)` is NULL, but I find the
whole thing totally bizarre. Is it me?
Yes, just you. None of the rest of us have any problems with this at all :-)
--
Richard Huxton
Archonet Ltd
--
Sent via
(good for
multi-user setups).
Cons:
- Extra layer of indirection (find my namespace = namespace lookup =
object)
- Extensions need to list what they export in what sections
- More code required
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers
(see upthread) that he uses
for the Bricolage docs does, however.
Ah, if you can change the overall layout then the world is your
shellfish of choice. Would it be possible to include jquery? It's
GPL/MIT dual-licence.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list
--
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/off.
The menu could be as simple/complex as you like - this is just what I
hacked together by parsing the TOC on index.html
I've tested it on Firefox, Opera, IE7 and Safari. Realistically, the
only real problem platforms will be IE6 and perhaps iphones.
--
Richard Huxton
Archonet Ltd
, or something else here?
--
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
Andrew Dunstan wrote:
Richard Huxton wrote:
Andrew Dunstan wrote:
Yes, really. What you suggest here is just not adequate, IMNSHO. I
don't want to have to scroll to the top or bottom of the page to get
navigation, and I want to be able to see the navigation and go where
I want directly
patch goes over the limit it goes in the next commit-fest.
--
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
and probably installed by default,
but they need not be hardcoded into the backend.
Presumably would help the prospective upgrader too. Upgrade tool can't
cope with the change to inet types? No problem, I *know* they're not in
use, since they're not loaded.
--
Richard Huxton
Archonet Ltd
--
Sent
, but
the idea is to map extension name to a schema. If possible, this should
work anywhere in PG that a schema can be specified.
So - If extension foo is installed in schema1 then ext:foo.fn1() is the
same as schema1.fn1()
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list
settings, character set and
locale details might be relevant too.
--
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
Windows-related difficulties there's no standard tools we can use to
diagnose.
--
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
=1804, addr=0170): 487
--
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
;
-- This works, though notice we treat the function as a row-source
SELECT (f1(a,b)).* INTO b,c;
RAISE NOTICE 'a=%, b=%, c=%', a,b,c;
RETURN true;
END;
$$ LANGUAGE plpgsql;
SELECT f2();
ROLLBACK;
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql
to spot it.
--
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
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 d...@archonet.com [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_start, time_start, txid_end
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 make changes to your subscription:
http
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 via pgsql-hackers mailing list
,
but might still allow very slow proof attempts in other large cases.
The specific narrow hack I'm considering for #3 goes like this:
The specific hack goes right over my head :-)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
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
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
when
you're about to remove a tuple that's still visible to some snapshot,
just the action is different. We should probably provide a GUC to
control which you want.
I think there's only one value here: hot standby wal delay time before
cancelling query. Might be a shorter name.
--
Richard
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 LEVEL SERIALIZABLE? Presumably the read
is disallowed then too?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql
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_emails
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
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
on
TOAST) so not readable as plain-text.
--
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
Tom Lane wrote:
Richard Huxton [EMAIL PROTECTED] writes:
Tom Lane wrote:
So put forward a worked-out proposal for some other behavior.
IMHO the time a dump/restore should be issuing ALTER...SET on a database
is when it has issued the corresponding CREATE DATABASE.
So pg_dump would produce
Robert Treat wrote:
On Tuesday 01 July 2008 03:45:44 Richard Huxton wrote:
The only time we need to restore per-database settings is if the
database has been dropped. If you're not having the dump/restore
re-create the database then presumably you've taken charge of the
per-database settings
the database with
whatever options you want and don't use --create.
I'm also wondering why it'd be bright to treat ALTER ... SET properties
different from, say, database owner and encoding properties.
Not sure what you mean here.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers
trap of a mind letting something like this slip through. Obvious
problem settings would be: datestyle, locale, default-text-search
Is this a deliberate behaviour of pg_dump or just an unscratched itch?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Tom Lane wrote:
Richard Huxton [EMAIL PROTECTED] writes:
Is it desirable that pg_dump doesn't dump config settings set via ALTER
DATABASE?
Well, it's intentional anyway: that's handled by pg_dumpall. The basic
design is that anything that can be seen from outside a specific
database
Richard Huxton wrote:
At present it means you can't reliably do:
DROP DATABASE foo;
pg_restore --create foo.dump
I'd then have to either hand edit the dumpall dump or wade through a
bunch of errors checking that none of them were relevant.
Actually, I'm not sure pg_dumpall does them either
Richard Huxton wrote:
Richard Huxton wrote:
At present it means you can't reliably do:
DROP DATABASE foo;
pg_restore --create foo.dump
I'd then have to either hand edit the dumpall dump or wade through a
bunch of errors checking that none of them were relevant.
Actually, I'm not sure
then the foreign-keys can be skipped.
If the restore checksum doesn't match the dump then it can issue a
warning, but continue and run the full fkey check.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
now.
So ... back to your regularly scheduled development.
Is there a tag in the CVS to mark this point, or better still a tarball
that people like me can check out and play with over the next month or two?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql
psql \h only gives me:
Syntax:
ALTER VIEW name RENAME TO newname
Ah, you use ALTER TABLE:
ALTER TABLE my_view ALTER COLUMN view_column DEFAULT expr;
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
in it. Try:
ALTER TABLE test ADD COLUMN id3 integer NOT NULL default 0;
--
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
experience in the last decade (one tsearch
parser) you don't want to just plug that into the live site. Someone
(Gevik?) was going to have a look at it when they had the time, but I'd
guess that's the one thing none of us have much of.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers
Magnus Hagander wrote:
Did you ever post the code to anybody other than Gevik? If not, please
send it to pgsql-www and someone can give it a quick look-over (perhaps
Oleg can help us there?)
Will do.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers
to back-patch the default parser for 8.4? At present,
it can't handle underscores in file-paths.
--
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
that postmaster actually started and continues to
print
It's not getting confused and thinking the port is 5432 -i is it? I
tried -i -p 5432 and that seemed to work.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Richard Huxton wrote:
Tatsuo Ishii wrote:
Hi,
I have encountered a strange pg_ctl's behavior in 8.3.
pg_ctl -w -o -p 5432 start-- works
pg_ctl -w -o -i start-- works
pg_ctl -w -o -p 5432 -i start-- doesn't work
In the last case, even postmaster starts successfully, pg_ctl keeps
Richard Huxton wrote:
Hmm - that does seem to be the case. I added a line to print connstr
along with the .
waiting for server to startdbname=postgres port=5483 -i
connect_timeout=5.
The code looks fine to my uneducated eye though (bin/pg_ctl/pg_ctl.c
test_postmaster_connection
| f
998 | requests | 'request' | f | t
997 | site | 'site' | f | t
996 | document | 'document' | f | t
(5 rows)
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
| 'tender' (1 clause)
(13 rows)
So - is this a bug, feature, feature?
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.orgextra=pgsql
function - presumably it's all down to context on the initial
parse.
I can't think of a way to exploit this maliciously, or do anything other
than cause a little confusion, but I'm not sure it's intentional.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-hackers mailing list (pgsql
Teodor Sigaev wrote:
So - is this a bug, feature, feature?
It's definitely a bug:
select count(*), query from queries group by query;
count | query
---+--
3 | 'tender'
4 | 'tender'
4 | 'tender'
(3 rows)
Will fix it soon.
Ah, smashing.
--
Richard Huxton
it to the various lists line 30-194,
then add the relevant TParserStateActionItems.
Thanks
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your
[EMAIL PROTECTED] wrote:
I have the following table:
The hackers list is for development of the PostgreSQL database itself.
Please try reposting on the general or sql mailing lists.
--
Richard Huxton
Archonet Ltd
---(end of broadcast
Tom Lane wrote:
Richard Huxton [EMAIL PROTECTED] writes:
Would there be any support for two changes in 8.4 though?
1. Tag tsvector/tsquery's with the (oid of) their configuration?
2. Either warn or require CASCADE on changes to a
configuration/dictionary that could impact existing indexes
ideas.
More details are described below.
Were you looking to hire developers, or do you have customers who are
looking to hire developers?
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project
Magnus Hagander wrote:
On Tue, Feb 19, 2008 at 03:53:11PM +, Richard Huxton wrote:
Magnus Hagander wrote:
What I'd really like to see is something like a new keyword on the SET
command, so you could to SET PERMANENT foo=bar, which would write the
configuration back into postgresql.conf.
I
1 - 100 of 346 matches
Mail list logo
