towards.
Thoughts? (Apart from jokes about having a WHY clause...)
Nice work, hope my comments will be helpful.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
,
but barring that, the SSL info is very handy when you're working on SSL
enabled servers.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Friday 18 April 2008 00:24, Joshua D. Drake wrote:
On Fri, 18 Apr 2008 00:21:58 -0400
Robert Treat [EMAIL PROTECTED] wrote:
We could just do:
psql 8.1.10 - postgresql server version 8.1.10
Type: \h for SQL help, \? for psql help, \q to quit
postgres=#
I think it's
the .psqlrc file. :-)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. This way you keep
the spec behavior for the spec syntax, and have a clearly non-spec command
for non-spec behavior.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Thursday 24 April 2008 23:40, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Perhaps a better option would be to implement Merge per spec, and then
implement a replace into command for the oltp scenario. This way you
keep the spec behavior for the spec syntax, and have a clearly
.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
for the backup scenario.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a trigger?
I have a generic version of this in pagila.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it can be deleted.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it in C,
but there are lot of users, that could use only plpgsql.
I think nod's toward PL/SQL compatability should be given in general. If
people want a PSM style language, let's work on getting pl/psm better
maintained or integrated.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache
party
uptake of the set, it might be better to get something in sooner rather than
later, so yes, we'd be happy to see the patch set adopted upstream./chime
--
Robert Treat
Database Architect
http://www.omniti.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
bits. Seems like more work with less
upside that read-only slaves vs. pitr warm standby we have now.
Interesting that core views this differently.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers
beyond 8.4.
Now it is possible that the time frame could be sooner, but unless someone
already has the patch, this reminds me a little too much of the arguments for
including windows support in a single release because we already had a work
port/patch set to go from.
--
Robert Treat
Build
. (Note I say address, not solve).
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tuesday 03 June 2008 01:17:43 Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Anyone see any issues with this?
I'm a bit worried about breaking diff-equality of matching dumps,
If you are calling pg_dump with different flags, it seems likely your breaking
diff equality anyway so
that needs to be distriubuted with the core? I'd lean
towards reviving the dtrace project on pgfoundry, but it might be worth
expanding the dynamic tracing chapter to include more examples and a pointer
to pgfoundry.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware
On Wednesday 04 June 2008 15:48:47 Andrew Dunstan wrote:
simply remove all the comment lines from your
config file.
+1. That would clear up a lot of confusion on it's own.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list
other DB's
strictly through graphical interfaces (something we are rather lacking in
ability to do comparativly). consider also that if this is built atop the
current pg_settings, all the normal sql tools can still help... ie.
pg_dump -t if you want to check something into svn.
--
Robert
buffer
restart scenario). I think most of the user base would like to approach
administration from that point-of-view, and as of yet I haven't seen a
technical reason why that world view is wrong, only philosphical ones.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware
something showed up... you could probably find that in the
archives if you look around.
of course to me this sounds like an excellent idea for a dtrace probe ;-)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers
to
just populate the search bot with every guc anchored to family though...
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
making the change though... not sure in
which way you would slant the output though.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Friday 06 June 2008 14:32:27 Robert Lor wrote:
Robert Treat wrote:
certainly by the time 8.4 ships, these should work with freebsd I'd
think. ideally we would need to confirm this by release time, certainly
getting a bsd buildfarm member to compile with them would be a start (and
very
actually) and it really helps working around having
to hold locks on large relations for lengthy periods of times. Heck, I'd like
to see a no check option for all constraints really.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing
the check.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sunday 08 June 2008 19:07:21 Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
On Fri, 2008-06-06 at 20:19 -0400, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
Actually, the reason it's still 10 is that the effort expended to get it
changed has been *ZERO*. I
On Sunday 08 June 2008 20:12:15 Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
and i'm sure no one is against that idea, but you're never going to be
able to match the performance of just avoiding the check.
We'll never be able to match the performance of not having transactions
(to
handle normal constraint, not null constraints, etc...), it would certainly
be a big win, and i think most would see it as a reasonable compromise.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers
will
be in, but since it does know what encoding template0 friends will be in,
and most databases are copied from those (including encoding), wouldn't a
better default be to set it the encoding of template0?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via
On Thursday 12 June 2008 17:38:26 Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
looking in my freshly installed 8.3.3, I see this in the postgresql.conf
#client_encoding = sql_ascii# actually, defaults to database
On Thursday 12 June 2008 21:11:57 Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
looking in my freshly installed 8.3.3, I see this in the
postgresql.conf #client_encoding = sql_ascii# actually,
defaults to database # encoding
But isn't putting a default
ISTM we need something that can run inside the db as well, i'm thinking
something like pg_check_conf() to go with pg_reload_conf(). Also, these
should probably check validity of the pg_hba.conf as well.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent
nicer than doing the whole
logging/analyze piece.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sunday 15 June 2008 22:31:59 ITAGAKI Takahiro wrote:
Robert Treat [EMAIL PROTECTED] wrote:
On Friday 13 June 2008 12:58:22 Josh Berkus wrote:
I can see how this would be useful, but I can also see that it could be
a huge performance burden when activated. So it couldn't be part
plenty of ways to list your contributors. Also, don't forget we allow
contributors to list companies next to thier names if they so desire.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
with this if we ever decide to make it
the default setup)
/broken record
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
for years now, while module support is still vaporware.
However, I am looking forward to your patch. :-)
BTW, I am suspecting part of your support will be giving pg_dump -m and -M
flags to control dumping or ignoring of specific modules?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache
there are other places this might manifest itself besides
pg_stat_activity... I'm struggling to come up with something other than our
custom dtrace prob... ah, well, this will also control the size of statement
written into the logfile right? So we might want to take that into account.
--
Robert Treat
part fails, they all fail.
Well, wrapping the bits of table2 in a beginexception block would allow
him to do what he wants.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
of people I have talked to, but I don't have
much hope in seeing the behavoir change... perhaps someday if we get around
to merging pg_dump and pg_dumpall
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers
are creating the database
manually. (Now, one might argue that you could still dump with --create and
ignore the error of the database creation command, but that probably isn't
ideal).
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers
it
interferes with your golf game.
https://www.redhat.com/archives/fedora-devel-list/2008-June/msg01501.html
So is that a golf club gun?
Careful what you wish for
http://www.totallyabsurd.com/12gaugegolfclub.htm
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
put your names on the stuff you know
you can review now.
Note that Robert Lor has an updated patch for the dtrace probes that we have
seen over here @ omniti, but I don't think he has posted it yet, so it isn't
reflected in the wiki... Robert, care to post that?
--
Robert Treat
Build
the July commitfest entry to point to this patch, case anyone wants
to review it.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Index: src/backend/access/transam/clog.c
===
RCS file: /projects/cvsroot
wonder if there should be additional
hurdles in place to enable this on that platform. Note that isn't an
objection from me, though I'm curious if any of the Sun guys want to chime in
on this.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers
to be better about linking to that and the various
commmitfest pages within the wiki itself. Right now it's a bit disorienting
trying to find your way around within the wiki itself well, maybe I will
get some time to fix that in the next couple of days.
--
Robert Treat
Build A Brighter
to sound like submitting a patch involves two steps from now on;
email to the list, and add your patch to the next commitfest page. Does that
sound right?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Saturday 05 July 2008 18:07:46 Robert Treat wrote:
On Thursday 03 July 2008 15:12:08 Joshua D. Drake wrote:
On Thu, 2008-07-03 at 20:06 +0100, Dave Page wrote:
On Thu, Jul 3, 2008 at 8:02 PM, Marko Kreen [EMAIL PROTECTED] wrote:
On 7/3/08, Dave Page [EMAIL PROTECTED] wrote
, but see up thread where Tom disagreed
with this idea.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that is just
going to break things when the first connection happens. For that matter,
why would we ever not want to parse it at HUP time rather than connect time?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql
are trying to solve,
and see if there are better tools they can be given to solve them. Barring
that, I suppose a crude solution is better than nothing, though I fear people
might point at the crude solution as a good enough solution to justify not
working on better solutions.
--
Robert Treat
Build
On Monday 04 August 2008 03:50:40 daveg wrote:
On Sun, Aug 03, 2008 at 10:57:55PM -0400, Robert Treat wrote:
ISTR that what ended up killing the enthusiasm for this was that most
people realized that this GUC was just a poor tool to take a stab at
solving other problems (ie. rate limiting
On Monday 04 August 2008 16:49:43 Simon Riggs wrote:
On Mon, 2008-08-04 at 14:35 -0400, Robert Treat wrote:
On Monday 04 August 2008 03:50:40 daveg wrote:
And you'll note, I specifically said that a crude tool is better than
nothing. But your completely ignoring that a crude tool can
On Monday 04 August 2008 15:56:25 daveg wrote:
On Mon, Aug 04, 2008 at 02:35:07PM -0400, Robert Treat wrote:
On Monday 04 August 2008 03:50:40 daveg wrote:
That's great for you, I am talking in the scope of a general solution.
(Note I'd also bet that even given the same hardware
Managers for each CF... is that not the case?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tuesday 05 August 2008 04:36:24 Magnus Hagander wrote:
Robert Treat wrote:
On Monday 04 August 2008 15:38:35 Josh Berkus wrote:
Post-mortem things we've learned about the commitfest are:
1) It's hard to get anything done in June-July.
True... vacations and conferences abound
as PGC_SIGHUP, and a change to the location would move the
file on-the-fly as they say. (There might be practical limitation to making
that work, but it would certainly be simpler for admins, imho)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql
, I'd be happy to spend some time making this work
better. :-)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
pg_get_keywords() works but SELECT * FROM
pg_show_all_settings() does not.
If this isn't critical, and no one is working on it yet, I can see about
whittling away at it for 8.4.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers
be turning this off?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. If people really don't like large conf
files, it is far easier to delete entries than it is to add them... Greg
Mullane had it right, and Greg Smith was not too far off the mark either.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers
On Wednesday 20 August 2008 02:22:26 Jaime Casanova wrote:
On Tue, Aug 19, 2008 at 9:40 PM, Tom Lane [EMAIL PROTECTED] wrote:
Robert Treat [EMAIL PROTECTED] writes:
I'd still like to see us adopt the proposal from some time ago where
we stop commenting out the parameters at all, but short
are not dumped with
the other installation wide settings. Meaning that pg_dumpall -g has no
bearing on the alter database commands being set, you actually have to
dumpall the entire data set to get those lines.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
directory would be helpful.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tsearch in it's own schema, so I can
easily seperate it with pg_dump.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
to core or to pgFoundry. Adding yet
another important feature that's just in contrib is making things
worse, not better.
IMHO, of course ;-)
+1. I felt the same way about pg_standby, which would have been far more
accessible for 8.2 users had it lived on pg_foundry.
--
Robert Treat
Build
of F.A.Q. is little bit obsolette.
The FAQ's *are* managed in html, though we also keep a spare copy as plain
text for historical reasons. See doc/src/FAQ/
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast
://ftp.postgresql.org/pub/projects/pgFoundry). If it was to go on
pgfoundry (which I'd recommend) I'd suggest removing it from 8.3 contrib
before we release (cause having it in both places is really going to cause
confusion)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
On Wednesday 10 October 2007 10:57, Andrew Dunstan wrote:
Robert Treat wrote:
On Wednesday 10 October 2007 02:09, Simon Riggs wrote:
On Wed, 2007-10-10 at 01:14 -0300, Euler Taveira de Oliveira wrote:
Simon Riggs wrote:
I would prefer that we backported pg_standby into 8.2 contrib, so
now that we have?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
any pressure, but this fix had me wondering if we might see an
8.2.6 before 8.3 is out?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
creating a tablespace on tmpfs or ramfs or something
like pramfs
FYI, Postgres is know to be used successfully on some *extremely* heavy
websites, without using tables pinned in memory.
+1
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
person entering the query anyway,
because there are layers of software between him and the DB. All they
will accomplish is to bloat some logs somewhere.
Comments?
I would lean toward #1 since it seems to be closest to the behavior from
previous releases.
--
Robert Treat
Build A Brighter LAMP
of notice (and
given the lack of back patches, should be too much of a burden in that time
either)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL
lists, or
involving the central project.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
people is removed
eventually, which doesn't happen with release notes.
Unless it's been changed, I added the past contributors section just for the
purpose of giving a historical credit and ongoing thanks for past
contribution.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware
| 2007-12-09 11:25:52.923612
If you store without timezone, you lose the original timezone information, so
selecting out with time zone simply selects the stored time in the time
zone you selected. HTH.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
, but in any case is there some reason it can't print out the proper
user name (maybe some encoding issue?)
3) as far back as I can remember, -u has been deprecated, so if we dont want
to revert to it (see 1) maybe it should just be removed entirely?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache
to the regular
mailing lists for help (which contrib authors may not follow).
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do
On Sunday 09 December 2007 13:33, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
1) I don't recall why -u was ever deprecated (and honestly postgresql is
the only program I know which uses -U rather than -u) but maybe we should
revert to -u and deprecate -U instread?
You appear
On Monday 10 December 2007 10:16, Tom Lane wrote:
Further down the road, those whose notion of intuitive was formed
by mysql might lobby to have -u become an alternate spelling for -U,
crontab, truss, sudo, ps, strace, top, etc...
--
Robert Treat
Build A Brighter LAMP :: Linux Apache
to manage this, which as of yet I am skeptical.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
the
partitions. If using segment exclusion on it meant that I could get a global
index to help that query, I'd be happy.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched
segment
exclusion to handle what is currently handled by partitions, and create
a global index across all the other data for that other, currently killer,
query.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast
), but not partitioning?
Yes, but aiui, SE should allow seq scans to achieve performance similar to
partitioning, especially if the planner can exclude segments based on values
in the data.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
on thier
accuracy), but that's more a style thing:
http://www.cs.helsinki.fi/u/laine/postgresql/programmer/arch-pg.htm#PGARCH-CONNECTIONS
http://www.postgresql.org/docs/7.3/static/arch-pg.html#PGARCH-CONNECTIONS
http://www.postgresql.org/docs/8.3/static/connect-estab.html
--
Robert Treat
Build
trigger that executes a DELETE, which then
fires row level calls.]
This seems to completly hand-wave away the idea of implementing row level
visibility in statement level triggers, something I am hoping to see
implemented somewhere down the line. Am I missing something?
--
Robert Treat
Build
, although that's rather ugly ;-) I'll commit this
change for now, but if anyone comes up with a simpler recipe I'll be happy.
Note we've been using Theo's plperl bytea patch on one of our production
servers for some time; if anyone wants access to that lmk.
--
Robert Treat
Build A Brighter LAMP
?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
)...
thoughts?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Wednesday 06 February 2008 13:56, Alvaro Herrera wrote:
Robert Treat wrote:
it looks as if the indexes on pg_class have become corrupt. (ie. reindex
claimes duplicate rows, which do not show up when doing count()
manipulations on the data). As it turns out, I can't drop these indexes
?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
hiss :-P
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
was read-only, so the behavior would be similar to
trying to edit it on the box as postgres user.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 5: don't forget to increase your free space
601 - 700 of 828 matches
Mail list logo
