), you might want to look into the hoops
we've jumped through lately to make pl/perl safe
(or rather, safer :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201007131614
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SI
cedural language, especially now that
it is enabled by default in the next version. :)
Thanks to everyone for staying calm and reasoned in this thread. I'll
have to try harder with my PHP baiting next time.
- --
Greg Sabino Mullane g...@turnstep.com
iter. Backslash!
Okay, that last one isn't a major strike, but it's damn annoying (and
indicative of the poor design of the language :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201006220936
http://biglumber.com/x/web?pk=2529DF6AB8
initial copying is done.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201006141048
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkwWQUAACgkQvJuQZxSWSsjMiQCc
r, pg_migrator (aka pg_upgrade)
might work for you as well: it does an inplace, one-time upgrade but only
supports a limited number of versions at the moment.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201006110927
my mutt[1] is more than happy to automatically pipe
things through lynx -dump which works pretty well. That said,
+1 to bouncing email with no text at all.
[1] Technically, mutt and mailcap
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP K
ize EXPLAIN on a
> query embedded in a stored function? I could run it just fine on the raw
> sql, but the raw sql wasn't what was running slow, so I'm not sure if it's
> even helpful to do that.
I wrote a blog article about this: Google for "Why is my function slow?&qu
anch.
(The above glosses over a few details between the systems, but
it's mostly a moot point now as pre-8.3 systems are becoming
relatively rare)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 2
be as straightforward and error proof
as the line you gave, I suspect.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005101331
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9
se a sequence at all. Again, seeing some
code would go a long way here.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005050928
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4B
g. Savepoints will nest (or shadow). The ON_ERROR_ROLLBACK
feature creates the savepoint before the query, then either does a
ROLLBACK TO or a RELEASE depending on the success of the query, so there
is no build up of savepoints.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporatio
owever, you'll probably want to setup cascading
slaves and use more than one daemon when the number of slaves climbs over
10 or so.
* Slony has a log shipping option that might be good for this use case.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http:
or the first time (if exists) and claiming the
first prepare when in fact it is reusing (else).
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004220922
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964
efaults to a too-nice mode when you really want immediate.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004021435
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN P
provement, and should be a TODO if not already.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201003091022
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkuWZ88ACgkQvJuQZxSWSsgVvgCfaWaOqcJEzfKBQiN5ttvU/EMB
lV
42976/en-us
Wow. If I even had the slightest regret about my move to abandon
Windows years ago, this would have pretty much squashed it.
Magnus et. al., I don't know how you do it. :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201003032043
http://biglumber.com/x/web?pk=
ngs would break before
you got to that point. See:
http://groups.google.com/group/pgsql.general/browse_thread/thread/462c454345221267/f61926526b539036
or:
http://5z8.info/super-nsfw_cyd
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8
ion does not
support it, Vick, it should be noted here for the archives). The
session_replication_role was added in 8.3:
http://www.postgresql.org/docs/8.3/interactive/sql-altertable.html
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key
Well, I'd prefer to have the old versions, but I can handle the status quo. As
long nobody pulls versions before they are really dead again. :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 20100228
http://biglumber.com/x
es before the
client notices the NOTIFY? If so, that's very wrong - the time lag should be
measured in sub-second intervals, so perhaps your client is doing something
wrong.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002
* versions, or as a list
of the *latest* revisions? I've always assumed the latter was more important
that the former.
> As for an estimated end-of-life, yes, we could definitely add that.
> Now that we finally have it :-)
+1
>> Either way, please add 7.4 back in. :)
>
>Done,
f it were clearer what your
program is doing and where it is failing, particularly this bit:
"the client do SELECT query every several hundreds seconds"
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002010912
http:/
unsupported versions. Heck, maybe an estimated end-of-life date
field for all versions as well?
Either way, please add 7.4 back in. :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201001291229
http://biglumber.com/x
be listing 7.4.27. Further, shouldn't we be keeping
even 'unsupported' versions on this page, so (e.g. case of check_postgres.pl)
clients can check if they have the latest revision, even if the major/minor
combo is super old?
- --
Greg Sabino Mullane g...@turnstep.com
End Point C
nd a NOTIFY to let the
Bucardo daemon know that the table has changed.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201001200828
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
that outputted the info on a single
line and then called the script inside the backticks.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201001080924
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B90
n aside, if you are syncing *from* prod to test, your process is
badly broken. :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201001040747
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAktB46wACgkQvJuQZxSWSsgW
the query plans that my
> functions are using?
See my blog post on this:
http://blog.endpoint.com/2008/12/why-is-my-function-slow.html
It's also in the first page of hits when you google the subject
line of this thread. :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
n
practice, you'll find that both are surprisingly quick.
With Bucardo, the number of changes may be much less than 1000, as it
is data based, not statement based. Thus, as an extreme example, if
the 1000 statements are all updating a single row, only a single
update (actually a delete/inser
ll have to recopy the entire table data to the slave, as the
triggers won't be in place yet.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 200912171153
http://biglumber.com/x/web?pk=
;m curious here to find areas we can improve upon.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 200912170927
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEY
al_file_contents read_file('/tmp/gtest');
RETURN 'GOT:' || external_file_contents;
END
$bc$;
SELECT gtest();
===
Piping all of the above into psql gives:
Output format is unaligned.
Showing only tuples.
Tuples only is off.
Output format is aligned.
CREATE FUNCTION
CREATE FUNC
ace that ld can see it. See the section on
"PostgreSQL library issues" in the DBD::Pg README for possible ways
to solve this.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 200911201309
http://biglumber.com/x/web?pk=2529DF6AB8F794
different versions of Postgres, no problem.
Unlike Slony, there is only a single master Bucardo daemon that can live
anywhere, even a box that is not the master or slave, as long as it can
talk to both.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 2009111417
s inside DBD::Pg
right after the initial connection:
$dbh->{pg_server_prepare} = 0;
This will prevent DBD::Pg from using server-side prepares. There's a small cost
to this, but it's usually overshadowed by the efficiency savings of using
pgbouncer.
- --
Greg Sabino Mullane g...@t
for a flag to pg_dump to
exhibit the behavior you want. It has a small chance of being accepted,
but a much greater chance than changing the default behavior.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200910251638
http://biglumbe
at some EDB people - did that ever happen?
I seem to recall we fixed that particular problem as well
during the codeathon at OpenSQL Camp.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200909102039
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067
e a real
crash, you should do a real crash. In this case, kill -9 the backend(s).
A server crash is a pretty rare event in the Postgres world, so I
would not spend too many cycles on this...
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200908
sequence is
getting near its maxvalue, and thus have an idea of when it is about
to cycle. The check_postgres program can do this for you:
http://bucardo.org/check_postgres/check_postgres.pl.html#sequence
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 2009
replication sense, but
if you have sites that are flaky, you might want to look at Bucardo:
http://bucardo.org/
It does master->slave (like Slony), but also does master<->master if
you need it.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8
so. Perhaps you can attack
this from another angle, such as using some sort of filter or script
to grab every X lines from the logs and discard the rest while in
full logging mode. That would have the advantage of being fully
backwards-compatible and usable today.
- --
Greg Sabino Mullane
uncer, spread the
tables and indexes across different tablespaces, and other tricks. If
money is tight, you might look into using something like EC2.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200907141552
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B
(and creating a savepoint for every execute
attempt), and silently encouraging SQL that will fail when fed to Postgres
through any other interface.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200907141125
http://biglumber.com/x/web?pk=2529DF6AB8F
ally good master-multislave) you
can evaluate (and get support for) Bucardo:
http://bucardo.org
As with all replication systems, there are some things it does better
than other systems (i.e. MySQL's), and some things it does worse.
- --
Greg Sabino Mullane g...@turnstep.com
End Poin
which is now the best place to track the issue:
https://rt.cpan.org/Ticket/Display.html?id=44461
Thanks for reporting this and for following up once discovering the AutoCommit
part.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200903220006
http://
me. What version of DBD::Pg are you using? Try something
recent if you are using something old. You can also set the trace
level to see what's going on behind the scenes:
$dbh->trace(10)
If you can't get it to work, please send a small, self-contained script that
duplicates the pr
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Is there a reliable way to find out the (Unix) PID associated with a
> database handle generated by Perl DBI's database connection?
$dbh->{pg_pid}
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP K
ange_(software)
http://www.icdevgroup.org/
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200902131158
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkmVps8ACgkQvJuQZxSWSsguGACgvcDGsH5u0r
ware, some settings /can/ be changed per
database with:
ALTER DATABASE prod SET random_page_cost = 2;
ALTER DATABASE fooz SET work_mem = '32 MB';
Not the logging and shared_buffers though...
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 200902081214
http://biglumber.com
bike shedding and making simple solutions complicated.
* Would like to see information_schema expanded.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 200902072156
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATUR
ckage just to have access to it.
>> BTW I ran into the need for pg_config upon installing DBD::Pg.
>> Maybe DBD::Pg maintainer problem?
> Installing a package for DBD::Pg or building it? The former would indeed be a
> package bug.
AFAIK, no package has that problem. If there is
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200811241506
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkkrCZsACgkQvJuQZxSWSsgHuwCeJmMj9oRxKP5uQ+DA5KNvCnzO
QbIAoJtEzOpT8Bi63Z/yvoAMtHpJdcfF
=Hh+m
-END P
th MySQL, which makes
open-source databases in general look bad when people familiar with Oracle
examine MySQL and assume Postgres is similar in attitude, community,
features, and robustness.
I'm sure EDB could expand this list a bit as well. :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP
en we get a new version out.
Thanks for the report: I was able to duplicate it, and have added it
to the test suite (still an unsolved failing test, but that's the
first step!)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200807111559
http://biglum
ush to get a new version out the door, but
there has not been much movement on it lately.
> Doing select * from pg_settings (with shared_preload_libraries defined
> and no custom variable definitions) causes a server reset.
Thanks, I'll see if I can duplicate.
- --
Greg Sabino Mullane
/Manual:Upgrading_Postgres
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200806041024
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkhGpcAACgkQvJuQZxSWSsgcPACgqDlcqt4dxfgwRfyehMuBy0lZ
b9sAnjBax4Na
h the
tsearch2 compatibility stuff. I'm creating some workarounds, and
will report back. Doing a --data-only dump and creating the schema
anew from maintenance/postgres/tables.sql should work, although
not if you've made any schema changes, obviously.
- --
Greg Sabino Mullane [EMAIL PROTEC
wikimedia.org/enter_bug.cgi?product=MediaWiki
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200805301532
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkhAVk0ACgkQvJuQZxSWSshAQwCeOKq4OHXrCPbjC6ATtfncA7Wq
v2oAnR9k/ME
.
http://www.bucardo.org/bucardo.html#BucardoConflictHandling
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200804161143
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkgGHogACgkQvJuQZxSWSshdAACg6
CE: I am trigger two
psql:trig.example:53: NOTICE: I am trigger three
UPDATE 1
ALTER TABLE
ALTER TABLE
psql:trig.example:59: NOTICE: I am trigger one
psql:trig.example:59: NOTICE: I am trigger three
UPDATE 1
SET
psql:trig.example:63: NOTICE: I am trigger one
psql:trig.example:63: NOTICE: I a
s (I'm converting from 7.4.19 to 8.3.1),
> so apparently I'm missing something.
You want: SET session_replication_role to 'replica';
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200804091058
http://biglumber.com/x/web?pk=2529DF6AB8F79407E944
; "proper" way to do this.
See the new new session_replication option:
http://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-SESSION-REPLICATION-ROLE
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200804022021
ht
break at some future major version with lots of prior warning.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200803271839
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkfsIosACgkQvJuQZxSWSshqnQCg0s7YAnxtF6qbOEiYYBifCR
a TODO to figure out some cleaner way of handling this sort
> of thing ...
I think I smell a GSOC project
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200803121533
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9
but does not need perl_setup().
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200803121042
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkfX6+0ACgkQvJuQZxSWSsiFdQCg4WGmB4+InrL7E+7c8Tq82lFy
TFcAn2lQfSXJwO8LUQ9vZPf9ZStLdVHW
l, it /is/ problematic, especially for those that don't know Perl well,
but doc patches are welcome. :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 20080336
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN
mention that we are disabling all the triggers on
> a given table only done during a transaction; thus, it affects no
> one else.
Be careful: if you are directly manipulating the system tables,
you still run the risk of problems as the system tables are
not completely MVCC safe unless you lock them.
- Fix bad PG_INTEGER example in docs, thanks to Xavi Drudis Ferran.
(CPAN bug #31545) [GSM]
- Fix META.yml file. (CPAN bug #25759) [GSM]
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200802111802
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alvaro Herrera asked:
> Is there an existing Postgres group?
Yes, this one:
http://www.linkedin.com/e/gis/41621/0F3C7A53CCD6
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200802032251
http://biglumber.com/x/web
ntuitive. I think having
psql recognize /^help/i would be a nice first step. Hmm, off to
write a quick patch...
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200801201225
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067149
uing Oracle and Microsoft because of their products, and companies have
no expectation of doing so. It might be nice if they did, and some theorize
it would lead to better and more secure products, but the reality is that
with software, you are on your own. Any company telling you otherwise as
a re
essage. It got caught
up in a rule which prevents mail with subjects such as "subscribe"
or "help" from being sent to the main list without moderation.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200711291651
http://biglumber.com/x/web?pk=2529DF6AB8F79407E
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just as a followup, I reported this as a bug and it is
being looked at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key
re questions, bearing in mind that "replication" is
a fairly generic term with no one-size-fits-all solution.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200711160922
http://biglumber.com/x/web?pk=2529DF6AB8F79407E9444
thing like //i
shouldn't suddenly fail just because you added an accented
character. The other part of me says to just have people use plperlu.
At the very least, we should probably mention it in the docs as
a gotcha.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End P
have two processes
sharing a handle.
Note also that InactiveDestroy should not be your first choice. Far
better to do the forking before the database connection whenever possible.
If they both need access, you can also disconnect, fork, and have both
reconnect afterwards.
- --
Greg Sabino M
way to do it (we don't have finer-grained control than
the 'require' opcode), but we could probably dial back restrictions,
'use' it, and then reset the Safe container to its defaults. Not sure what
other problems that may cause, however. CCing to hackers for discussion
the
and fire off the sync when asked to. You
could even run a single Bucardo instance on the home and toggle the
databases from "active" to "inactive" status in the bucardo.db table.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 2007101511
" sync (master-master). If the rows truly
do not overlap at all (by PK), you may also be able to set it up as a
dual "pushdelta" (master->slave both ways).
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200
tica".
That name could be confusing - what about the people out there
who would be wondering if we'd support SQL or not? The name
should definitely be "HorizonticaSQL"
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200709081522
http://biglumber.com/x/web?pk=252
dn't use unsigned int or
unsigned long int here, both for ntups and the return value of the
function.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200707300937
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC
create a second one
by calling DBI->connect.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200707181533
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFGnmspvJuQZxSWSsgRAxjIAJ0TRN5bTs9s1/Z3/YC/
e this plperl example:
http://people.planetpostgresql.org/greg/index.php?/archives/2007/05/30.html
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200707070745
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIG
27; => '2007-07-06 20:07:53.22277-04',
'query_start' => '2007-07-06 20:08:15.37116-04',
'client_port' => '-1',
'client_addr' =&
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Anyone have an implementation of the Jaro Winkler fuzzy string
> matching algo for Postgres?
I've not seen one, but it should be a Simple Matter of Programming
to whip something up in Perl or C.
- --
Greg Sabino Mullane [EMAI
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Which list is the most appropriate for proposing features
> and ideas for postgres ?
Generally, -general. If the proposal is very technically specific,
you might prefer -hackers instead.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
P
but it seems a bit too much reinventing an
already existing wheel. I was amused to see the script had the ill-fated
Lee-Jackson-King day in it. Ideally, we'd want a Postgres table that
describes the rules for each holiday, and then a function that reads it
on the fly. Perhaps a projec
e same day every year (e.g. Easter) will trip
you up. A possible solution is to write a plperlu function that
makes a call to Date::Manip, which can tell you the number of
business days between two date while excluding holidays, and which
allows you to specify exactly which days are considere
g =~ s/\W/ /g;
return $string;
$_$;
SELECT to_tsvector(wordsplit('cat,dog apple/orange'));
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200704261140
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFGMMikvJuQZ
ould upgrade to 8.1.8.
You can add multiple rows in one statement like this:
INSERT INTO tab_name (col1,col2)
SELECT val1, val2
UNION ALL
SELECT val3, val4;
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200704031025
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B
UNION ALL SELECT 3,55.5 UNION ALL SELECT 3,11.0;
- -- Fails:
DELETE FROM hundred WHERE percent = 55.5;
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200703222156
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFGAzQ1vJu
ter, IMO) make it two separate arguments:
select foobar('baz', 'public');
I usually put the table first as it allows me to overload the function
with a single arg and a default schema.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 2
o set the PERL environment variable before running ./configure.
Not sure when this was added - if it doesn't work for your version
of Postgres, you can also fiddle with the PATH.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200703151208
http://biglumbe
ALTER TABLE foo RENAME TO "FOO"
Simple creating the table as "FOO" in the first place avoids the problem as
well.
Be aware that using uppercase identifiers means that *all* access to that table
must
now quote the name.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP
he problem.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200703042038
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFF63UNvJuQZxSWSsgRA6WQAJ9PhmXeuuxgfggMklXfo/Ph5A0qJQCeJgcN
TxaPV7RU5ETVBflXpRbcEB4=
=5qbK
l stores dates as
char(14).
For the record, anyone using wikipgedia deserves the pain they
get: it is deprecated. The latest version of MediaWiki itself is what
should now be used: it will detect if you have Postgres upon
installation. :)
http://www.mediawiki.org/
- --
Greg Sabino Mullane [
his occured on the
very same day as the original poster. The server was upgraded to 8.2.3,
after some creating-bogus-xlog-file pain to extract all the data, and
all is well again.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200702221021
http://biglumber.com/x/web?pk=2529DF6AB8F7
ect count from the table referenced by the
rule return a non-zero count? In other words:
SELECT count(*) FROM sessions_90 where id = currval('sessions_id_seq');
(or some other similar table) may show your "missing" rows. The other
possibility is that the you are not us
w possible? I looked at the docs without finding anything.
It is not currently possible, but it is being worked on as part of the next
version of DBD::Pg.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200701301513
http://biglumber.com/x/web?pk=2529DF6AB8F7940
--
Best language? Perl Best database? Postgres True answer? 42
(1 row)
sprintf
-
Total grams: 101.319 Donuts: chocolate and boston cream
(1 row)
sprintf
---
Arguments: 1
101 - 200 of 276 matches
Mail list logo
