SPARC system,
building 9.5.4 (+OpenSSL 1.1.0 patches).
[1] Compiler features by release:
http://www.oracle.com/technetwork/systems/cccompare-137792.html
[2] Pre-defined compiler macros:
https://sourceforge.net/p/predef/wiki/Compilers/#oracle-solaris-studio
Thanks,
--
Andy Grundman
. They know who they can contact
for help.
I think I like belts better (yellow, green, red, black).
I think this gives me two things:
1) permission to mess up
2) ability to measure myself
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=79b2ee20c8a041a85dd230c4e787bef22edae57b
So I was wondering if there is anything I can help with? Not sure if you need
a reproducible case, or something you'd like me to try?
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On 09/10/2011 11:43 AM, Thom Brown wrote:
On 10 September 2011 17:40, Andy Colsona...@squeakycode.net wrote:
I'm playing with 9.2devel, and I can fill my logs with:
WARNING: pgstat waiting for 5001623 usec (494 loops), file timestamp
368986878169601 target timestamp 368986897680812 last
On 09/10/2011 11:39 AM, Alexey Klyukin wrote:
Hi Andy,
On Sep 7, 2011, at 6:40 AM, Andy Colson wrote:
Hi Alexey, I was taking a quick look at this patch, and have a question for ya.
...
Where did the other warnings go? Its right though, line 570 is bad. It also
seems to have killed
no benefit from a packaged alpha release.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
use it. (I'm not 100% sure ANALYZE is better,
either).
I'm going to leave this patch as needs review, I think more eyes might be
helpful.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
works fine:
select * from test1(1);
set plpgsql.prepare_plans to on_start;
create or replace function test1(a integer) returns integer as $$
begin
return a+1;
end;
$$ language plpgsql;
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
the item.h comments to reflect the change. I
think the patch is ready for a serious review now.
Thanks,
Pavan
Hi Pavan, I tried to apply your patch to git master (as of just now) and it
failed. I assume that's what I should be checking out, right?
-Andy
--
Sent via pgsql-hackers mailing
warnings go? Its right though, line 570 is bad. It also
seems to have killed the server. I have not gotten through the history of
messages regarding this patch, but is it supposed to kill the server if there
is a syntax error in the config file?
-Andy
--
Sent via pgsql-hackers mailing
Tomas, I cannot seem to see any of the patches you link here:
https://commitfest.postgresql.org/action/patch_view?id=628
Looks like you need to take the out of the messageid.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
and reworked:
http://archives.postgresql.org/pgsql-hackers/2011-07/msg01041.php
but that was posted Jul 19, 2011. And the Patch linked from commitfest is Jun
6, 2011. So is that an old patch? Or a new patch?
I'm confused.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On 09/05/2011 12:17 PM, Andy Colson wrote:
Tomas, I cannot seem to see any of the patches you link here:
https://commitfest.postgresql.org/action/patch_view?id=628
Looks like you need to take the out of the messageid.
-Andy
This patch seems to solve the problem of going back in time
a look at the cache? Should this
be accepted as a short term fix (cuz someone will fix the cache later), long
term fix (cuz the cache needs to say as-is), or not at all (because someone
will fix cache right now now)?
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
, I have not used array's so not sure if there
are memory limits on them)
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Pavel, this patch:
https://commitfest.postgresql.org/action/patch_view?id=624
It applied clean and compiled ok, but I cannot get it to work at all.
$ psql
Timing is on.
psql (9.2devel)
Type help for help.
andy=# set plpgsql.prepare_plans to on_start;
ERROR: unrecognized configuration
On 09/05/2011 05:04 PM, Andrew Dunstan wrote:
On 09/05/2011 05:03 PM, Andy Colson wrote:
Pavel, this patch:
https://commitfest.postgresql.org/action/patch_view?id=624
It applied clean and compiled ok, but I cannot get it to work at all.
$ psql
Timing is on.
psql (9.2devel)
Type help
On 09/05/2011 05:27 PM, Andy Colson wrote:
On 09/05/2011 05:04 PM, Andrew Dunstan wrote:
On 09/05/2011 05:03 PM, Andy Colson wrote:
Pavel, this patch:
https://commitfest.postgresql.org/action/patch_view?id=624
It applied clean and compiled ok, but I cannot get it to work at all.
$ psql
be way faster, and you dont really
care what the number is anyway.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the set of things worth adding to the alpha4 release
notes.
Support unlogged tables. The contents of an unlogged table are WAL-logged;
um.. are _not_ WAL-logged?
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 03/05/2011 08:54 AM, Robert Haas wrote:
On Sat, Mar 5, 2011 at 9:44 AM, Andy Colsona...@squeakycode.net wrote:
Support unlogged tables. The contents of an unlogged table are
WAL-logged;
um.. are _not_ WAL-logged?
Uh, yeah. It looks like I fixed that in the version I committed
On 03/05/2011 08:54 AM, Robert Haas wrote:
On Sat, Mar 5, 2011 at 9:44 AM, Andy Colsona...@squeakycode.net wrote:
Support unlogged tables. The contents of an unlogged table are
WAL-logged;
um.. are _not_ WAL-logged?
Uh, yeah. It looks like I fixed that in the version I committed
On 3/3/2011 6:49 AM, Michael Meskes wrote:
On Wed, Mar 02, 2011 at 01:33:35PM -0600, Andy Colson wrote:
I thought Kris was going to work on this, but saw no progress, and I
was bored the other day, so I started working on it.
Here is a parse.pl, with some major refactoring.
I named
are welcomed. (oh, yeah, I probably
need to go add some documentation)
-Andy
#!/usr/bin/perl
# src/interfaces/ecpg/preproc/parse.pl
# parser generater for ecpg
# call with backend parser as stdin
#
# Copyright (c) 2007-2010, PostgreSQL Global Development Group
#
# Written by Mike Aubury mike.aub
at least.
Oh! Perl is my favorite. Kris, if you're not going to, I'd love to work on
this.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 01/23/2011 08:29 AM, Andy Colson wrote:
On 01/22/2011 09:28 PM, k...@shannon.id.au wrote:
On 23 January 2011 13:14, Andrew Dunstanand...@dunslane.net wrote:
But there are quite a few perlheads around. ISTR Matt Trout was muttering
about these scripts on IRC recently.
Ok, so I've figured
On 01/23/2011 10:06 AM, Andrew Dunstan wrote:
On 01/23/2011 10:16 AM, Andy Colson wrote:
On 01/23/2011 08:29 AM, Andy Colson wrote:
On 01/22/2011 09:28 PM, k...@shannon.id.au wrote:
On 23 January 2011 13:14, Andrew Dunstanand...@dunslane.net wrote:
But there are quite a few perlheads
This is a review of:
https://commitfest.postgresql.org/action/patch_view?id=468
Purpose:
Equal and not-equal _may_ be quickly determined if their lengths are different.
This _may_ be a huge speed up if we dont have to detoat.
The Patch:
==
I was able to read and understand
?
I marked my two reviews as ready for committer, but I feel like I've
overstepped my bounds.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 01/16/2011 07:14 PM, Alex Hunsaker wrote:
On Sat, Jan 15, 2011 at 14:20, Andy Colsona...@squeakycode.net wrote:
This is a review of plperl encoding issues
https://commitfest.postgresql.org/action/patch_view?id=452
Thanks for taking the time to review!
[...]
The Patch
This is a review of plperl encoding issues
https://commitfest.postgresql.org/action/patch_view?id=452
Purpose:
Your database uses one encoding, and passes data to perl in the same encoding,
which perl is not prepared for (it assumes UTF-8). This patch makes sure data
is encoded
I know its been discussed before, and one big problem is license and
patent problems.
Would this project be a problem:
http://oldhome.schmorp.de/marc/liblzf.html
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
, then time can be put toward it).
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
steps, but I wanted to get you #1 above.
-Andy
Ok, forget the time thing. Has nothing to do with it. (Which everyone already
assumed I imagine).
Its truncate.
Create unloged table, fill it, truncate it, fill it again, restart pg, and the
data will still be there.
-Andy
--
Sent via pgsql
messages from vacuum:
WARNING: relation ulone page 0 is uninitialized --- fixing
WARNING: relation pg_toast_16433 page 0 is uninitialized --- fixing
you create an unlogged table, fill it, restart pg (and it clears the table),
then fill it again, and vacuum complains. Here is a log:
andy=# drop
on that, I have a pgbench_accounts table (unlogged) that after a restart
has data in it.
andy=# select aid, bid, abalance from pgbench_accounts where abalance = 3305;
aid | bid | abalance
-+-+--
3790226 | 38 | 3305
274130 | 3 | 3305
2169892 | 22 | 3305
)
Total rows: 61,467,489
Total Seconds: 1,126.75
Total ins/sec: 54,552.60
After all this... there are too many numbers for me. I have no idea what this
means.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
also have a real world test I can try (import apache logs and run a
few stats).
What other things would be good to test:
indexes?
analyze/stats/plans?
dump/restore?
Is create temp unlogged table stuff(...) an option?
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
]
That didnt happen the first time... I'm almost positive.
Not sure what I should do now.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Jul 17, 2010, at 3:20 AM, Peter Eisentraut wrote:
On fre, 2010-07-16 at 10:31 -0400, Tom Lane wrote:
The other argument that I found convincing was that if the
operator was defined to yield numeric, people might think that
the result was exact ... which of course it won't be, either way.
On Jul 15, 2010, at 7:25 PM, Tom Lane wrote:
* I didn't like this bit in cash_numeric():
result-n_sign_dscale = NUMERIC_SIGN(result) | fpoint;
Not only is that unwarranted chumminess with the implementation of
numeric, it's flat-out wrong. If the result isn't exactly the right
On Jun 21, 2010, at 11:47 AM, Kevin Grittner wrote:
Yes, although the line endings are Windows format (CR/LF).
The line endings must have gotten changed in transit. My original diff used
just LF. I made it on a Mac.
The only issue is with the general guideline to make the new code
blend
Marc Fournier wrote:
But, I think you and I are exceptions here, in that we use the web interface
for moderation, and not just email ...
Is it possible that the ones that use email for moderating the lists have
aggressive spam filters? Then they might not receive most of the list postings
Thanks for the explanation of CommitFests.
On May 30, 2010, at 6:53 AM, Kevin Grittner wrote:
You would then generate a diff in context format and post to the
-hackers list with that file as an attachment.
I made my diff with src/tools/make_diff, as suggested in the Developer FAQ. But
On May 30, 2010, at 6:53 AM, Kevin Grittner wrote:
You would then generate a diff in context format and post to the
-hackers list with that file as an attachment.
Here it is:
dividing-money.diff
Description: Binary data
Don't forget to add
it to the CommitFest page:
On May 30, 2010, at 6:53 AM, Kevin Grittner wrote:
You would basically move the functions and their prototypes to cash.c
and cash.h, and then (instead of CREATE FUNCTION, etc.) add
corresponding entries to pg_proc.h and pg_operator.h. (If I'm
missing something, someone please jump in.) Of
I'm not quite sure how to go about changing it from an add-on function to a
built-in one. So if you want to do that, go ahead. If you'd rather I did, just
tell me how it's done.
Andy Balholm
(509) 276-2065
a...@balholm.com
On May 26, 2010, at 11:18 AM, Kevin Grittner wrote:
Hi Andy,
Do
nly
one sentence I think we should add it adjacent to the existing
sentence discussing remembering the index. My proposed patch
attached; thoughts?
As long as there's a pointer to the answer I'm happy.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
I couldn't figure out how to get rid of the CLUSTER flag on an index.
Once I got the answer from IRC, I wrote this patch to point future users
to the answer.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.petdance.com = AIM:petdance
diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src
I was looking for how to undo a CLUSTER call earlier today. Nothing on
the CLUSTER page told me how to do it, or pointed me to the ALTER TABLE
page. I figure a pointer to would help the next person in my situation.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.petdance.com
.]table
If you wanna see the data right from the shapefiles, you can use a tool
like qgis.
.dbf is regular dbase file
.shp is a shapefile (esri shapefile)
.shx is an index
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
) got any triggers or stored procs?
6) To the -hackers: I write the records and then refind them in the
exact same order, would it be a better test to search for records in a
more random order? would it make a difference? Would searching for
some but not all make a difference?
-Andy
--
Sent
Josh Berkus wrote:
Andy,
6) To the -hackers: I write the records and then refind them in the
exact same order, would it be a better test to search for records in a
more random order? would it make a difference? Would searching for some
but not all make a difference?
Are you on OpenSolaris
Greg Smith wrote:
On Wed, 27 May 2009, andy wrote:
I have a Sun blade 1000 that's just collecting dust now days...It
weighs a ton.
Bah, I know I picked one of those up myself once, which means it's far
from being what I'd consider a heavy server as Sun hardware goes. Specs
say it's 70
Jignesh K. Shah wrote:
On 05/27/09 22:00, Josh Berkus wrote:
Andy,
I have a Sun blade 1000 that's just collecting dust now days. I was
wondering if there were any pg-hackers that could find use for it.
Its dual UltraSPARC III 750 (I think) and has two 36? gig fiber channel
scsi disks
Greg Smith wrote:
On Thu, 28 May 2009, Andy Colson wrote:
Yeah, when it shipped I think it was about 75 pounds. It is a tower,
yes, and an impressively large box (my experience with servers is
limited, this is the first I've ever gotten to play with, so it may
not be out of the ordinary
Josh Berkus wrote:
Andy,
Yeah, when it shipped I think it was about 75 pounds. It is a tower,
yes, and an impressively large box (my experience with servers is
limited, this is the first I've ever gotten to play with, so it may not
be out of the ordinary). I think my kill-a-watt said, at idle
Andy Colson wrote:
Josh Berkus wrote:
Andy,
Yeah, when it shipped I think it was about 75 pounds. It is a tower,
yes, and an impressively large box (my experience with servers is
limited, this is the first I've ever gotten to play with, so it may not
be out of the ordinary). I think my kill
I have a Sun blade 1000 that's just collecting dust now days. I was wondering
if there were any pg-hackers that could find use for it.
Its dual UltraSPARC III 750 (I think) and has two 36? gig fiber channel scsi
disks.
It weighs a ton.
I'd be happy to donate it to a good cause.
-Andy
I've got my git clone set up, a copy of GCC 4.4 (and other compilers)
at the ready, and am glad to help out on low-level scut work. Anybody
need anything done? splint? valgrind? Let me know.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
for, the better.
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. I think it tells me quite a bit about the Postgres
world.
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
end. I'd rather that volunteers, especially new volunteers, spend
their time and brain cycles thinking about code, not messing with
config files.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers
there are plenty of projects that do use them to
great effect, most notably Perl 5 and Parrot. Perl 5 specifically has
had the mish-mosh of tabs-vs-spaces reduced by the addition of
modelines.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via
of
push-back. If he'd phrased it as would this be a good idea? then
I would have reacted differently.
But since he didn't, it's OK to be insulting?
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers
in Tom's
original mail.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
saying is that my
git repo does not have doc/FAQ_DEV. I didn't see it scroll by in the
CVS repo that I'm rsyncing, either.
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
.
--
Andy Lester = a...@petdance.com = www.petdance.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
file for Perl::Critic and a make
target for perlcritic.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I've got my git clone set up, a copy of GCC 4.4 (and other compilers)
at the ready, and am glad to help out on low-level scut work. Anybody
need anything done? splint? valgrind? Let me know.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
Getting our Perl into shape would be Really Good(TM). :)
I will, but right now my #1 is getting some vi modelines in place so
we can all be using the same tab/space settings.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com = AIM:petdance
--
Sent via pgsql
, it enforces proper file formatting for the
user without having to worry about local settings.
And if you're an Emacs person, you can help figure out what the
modeline should be for Emacs, and we can get that in there, too.
xoa
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com
On Apr 30, 2009, at 2:11 PM, David Fetter wrote:
Here's a patch that gets it to pass perlcritic -4 and still (as far as
I can tell) work.
Tell ya what. Let me at it and I'll give a larger, more inclusive
patch.
xoxo,
Andy
--
Andy Lester = a...@petdance.com = www.theworkinggeek.com
scripts to play around with inserts and updates
and compared a few timings on xfs vs ext2... and then kinda lost interest.
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
INDEX's for that table, while the first connection went on to
COPY the next table.
Or something like that...
-Andy
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Saturday 23 February 2008 00:40, Tom Lane wrote:
Andy Pavlo [EMAIL PROTECTED] writes:
I have added support in readfuncs.c to write out Query and PlannedStmt
objects using nodeToString() and then read them back in. We needed this
so that we could use PREPARE and write the arguments
of Postgres.
Thanks!
--
Andy Pavlo
[EMAIL PROTECTED]
---(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
?
I dont think the buildfarm needs to require CVS. The code can be
changed in the buildfarm to just run 'svn up' or 'git up and go' (sorry,
never used git so I had to guess at the command :-) ) right?
-Andy
---(end of broadcast)---
TIP 6: explain
Rapids, Iowa?
-Andy
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Alvaro Herrera wrote:
andy wrote:
with autovacuum enabled with default settings, cramd.sql is 154M:
[EMAIL PROTECTED]:/pub/back$ time pg_restore -Fc -C -d postgres cramd.sql
real3m43.687s
[...]
Now I dropdb and disable autovacuum, restart pg:
[EMAIL PROTECTED]:/pub/back$ time
2519 pts/0S+ 0:12 pg_restore -Fc -C -d postgres cramd.sql
2521 ?Ss 1:04 postgres: andy cramd [local] CREATE INDEX
waiting
2526 ?Ss 0:03 postgres: autovacuum worker process cramd
2571 ?Ss 0:01 postgres: autovacuum worker process cramd
2582 pts/1
---+--+--+-
andy | andy | LATIN1 | 4255 kB
cramd | andy | LATIN1 | 526 MB
postgres | postgres | LATIN1 | 4263 kB
template0 | postgres | LATIN1 | 4136 kB
template1 | postgres | LATIN1 | 4255 kB
(5 rows)
pretty nice, huh?
-Andy
--- src/bin/psql/describe.orig 2007-10-31 13:37
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
I know its way too late in the game, sorry, but it's a very small patch...
(1) What's the performance impact? I should think that this makes \l orders
of magnitude slower.
(2) Doesn't this render \l entirely nonfunctional for users who don't
if we had a \stats
that print stuff just about the db your connected to, and it could
probably find a bunch of other info to print besides just the dbsize.
-Andy
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Oleg Bartunov wrote:
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
Where would be an easy place to find all the renamed functions?
My experience with fts is limited to one project, and I just used all
the default dictionaries, so I've
automatic way to do that, but at the very least we need
some documentation about what corresponds to what.
I'm afraid the defaults have just worked for me, so I never played
with any of the config stuff (old or new)... I don't know if I'll be of
any help here.
-Andy
I have two doc updates I'd like to offer. I see we have two example
sections: creating rule-based dict's and creating parsers. When I was
starting I would have liked to see an example usage.
I'd like to offer: example usage and Upgrading.
This is my first draft, if anyone has suggestions I'd
Oleg Bartunov wrote:
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
Where would be an easy place to find all the renamed functions?
My experience with fts is limited to one project, and I just used all
the default dictionaries, so I've
Florian G. Pflug wrote:
andy wrote:
Is there any chance there is an easier way to backup/restore? On one
hand, its not too bad, and it'll only be once (correct?). Now that
fts is in core future backup/restores will work, right? I think it's
analogous to telling someone they are updating
OPERATOR public !! andy
1124; 2617 98024 OPERATOR public andy
1112; 2617 98003 OPERATOR public andy
1118; 2617 98017 OPERATOR public andy
1113; 2617 98004 OPERATOR public = andy
1119; 2617 98018 OPERATOR public = andy
1117; 2617 98005 OPERATOR public andy
1123; 2617 98019 OPERATOR public andy
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
the operator = is not the 'normal =' is it? Its the 'tsearch2 =', right?
That one probably is, but how is your sed script going to distinguish it
from other user-defined '=' operators that might be in the dump?
Do I need to worry about sed
question: I don't have to enable or install anything, do I?
Thanks,
-Andy
---(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
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but still
got a bunch of errors (those above). If I clean that up of all the old
text search stuff, and then run it, then do the data, will that work ok?
Further
Tom Lane wrote:
Andy Colson [EMAIL PROTECTED] writes:
I have an 8.2 database that has full text searching. I tried to
backup/restore it to 8.3 but got lots of errors:
...
I didn't really expect it to totally work, but I'm not sure how to move
my db.
Did the data transfer over
andy wrote:
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but
still got a bunch of errors (those above). If I clean that up of all
the old text search stuff, and then run it, then do the data, will
that work ok
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
Tom Lane wrote:
Did the data transfer over? The declarations of the former contrib
functions would of course fail, but type tsvector is still there.
I would like to think that ignoring pg_restore's whining would get
you most of the way
it could be avoided.
Really, isn't it just bulk loads anyway where a person might do this?
-Andy
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
in the tools directory. Is there anything else
this todo should address?
Thanks,
Andy
___
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com*** ./src
holiday season, and an incredible 2006.
All the best,
-- Andy
-
Andy Astor, CEO
EnterpriseDB Corporation
777 New Durham
Road
Edison, NJ
08817
Tel 732.331.1310
www.enterprisedb.com
concur with this. We ran into this with plPerl.
The only way to successfully extend PostgreSQL commercially is to
coordinate with the community.
-- Andy
---(end of broadcast)---
TIP 8: explain analyze is your friend
1 - 100 of 104 matches
Mail list logo
