difficult to manage.
--
Jonah H. Harris, Senior DBA
myYearbook.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Which Postgres ODBC driver are you using with heterogeneous services?
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837 | http://www.enterprisedb.com/
--
Sent via pgs
On Mon, Jun 2, 2008 at 6:16 PM, <[EMAIL PROTECTED]> wrote:
> Is there a way to protect the data files, so even the "malicious
> administrator" cannot see the data ?
Encrypt it. Though, how you store the key will be important.
--
Jonah H. Harris, Sr. Software Architect
> author and do not necessarily represent those of the company.
> The Company reserves the right to monitor, review and store the content of
> all messages sent to or from this e-mail address.
>
> www.aztecsoft.com
>
--
Jonah H. Harris, Sr. Software Architect | phone: 732.33
On Mon, Mar 24, 2008 at 6:56 PM, Jack <[EMAIL PROTECTED]> wrote:
> Is there a Postgres equivalent of tkprofs for tuning?
No. But what you could do is combine several Postgres things to try
and get the same information.
IIRC, you could use:
- log_parser_stats
- log_planner_stats
- log_executor_st
On Feb 5, 2008 11:54 PM, Decibel! <[EMAIL PROTECTED]> wrote:
> One of the things that drew me to Postgres years ago was that I could
> actually read about how it works in a clear, concise manner.
Agreed.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB
kend will cancel a query on them. As for killing the
process itself, use:
kill -TERM
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837
only; like it or not, most Windows people wouldn't easily be able
to script it.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837
; I get your argument but surely adding SCHEMA isn't that much of a code
> bloat scenario. We don't even have to add another reserved word...
Agreed. It's very simple and won't add much code at all.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
Enter
ever be the be all end all.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837| http://www.enterprisedb.com/
-
On Nov 30, 2007 2:46 PM, Campbell, Lance <[EMAIL PROTECTED]> wrote:
> Could you please add to your to do list a schema parameter for vacuum?
Schema-based analyze would also be useful.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Co
would there be if I increase this number to,
> say, 200? (and would that be a good idea?)
A little overhead, nothing bad.
> 5) finally, what's the best fix? (Do I need to go to pgpool?)
see pgbouncer
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB
posed to be a joke? Have you RTFM? Have you
looked at the code to pkill? pkill calls kill and frankly, pkill is
more dangerous if you only want to kill a single session.
Grr, I'm surprised to see such an uninformed statement on this list.
--
Jonah H. Harris, Sr. Software Architect | ph
er from Postgres when
> needed.
At this point in time, there isn't one.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison,
pick a procpid and kill right there...
Write a C stored procedure that takes a pid and calls kill(2), install
it on the server, and call it from SQL.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street,
required to
know if anything remains corrupted, but it is used occasionally. Best
to do pg_cancel_backend and then kill -TERM.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floo
gres-to-Postgres in contrib)
dblink_odbc (Postgres-to-ODBC on PgFoundry)
dblink_tds (Postgres-to-Sybase/SQL Server on PgFoundry [has a memory leak])
dbi-link (Postgres-to-DBD in Perl)
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.13
do it?
See pg_cancel_backend
You should also look at using statement_timeout if this is a regular occurrence.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor |
tate and
> they look very old...
What version of Postgres and IRIX are you running?
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837
e list?
Yeah, Josh B. asked it to be toned down to the original list which
should've been involved. Which I think should be pgsql-admin or
pgsql-advocacy... your thoughts?
I think the Oracle discussion is over, David T. just needs URL references IMHO.
--
Jonah H. Harris, Software Archit
ng the topic again? My vote is for
the latter; it served no purpose other than to push the
competitiveness topic again.
I haven't seen any bashing going on yet. Shall we start with the closed
mindedness and unfairness of per cpu license and support models?
Not preferably, you make me type
-list gospel.
All of us have noticed the anti-MySQL bashing based on problems with
MySQL 3.23... Berkus and others (including yourself, if I am correct),
have corrected people on not making invalid comparisons against
ancient versions. I'm only doing the same where Oracle, IBM, and
Mic
On 6/18/07, Andreas Kostyrka <[EMAIL PROTECTED]> wrote:
As a cynic, I might ask, what Oracle is fearing?
As a realist, I might ask, how many times do we have to answer this
type of anti-commercial-database flamewar-starting question?
--
Jonah H. Harris, Software Architect |
comparison.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 3rd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
---(end o
On 5/31/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
Or, you just use the features you pay for and use COMMIT NOWAIT.
Doh! Got mixed up on the conversation, that wouldn't help. But you
could use Oracle's in-memory UNDO, which would not be as costly as a
normal update.
--
27;t have to pay it while your user is sitting
there waiting for you.
Or, you just use the features you pay for and use COMMIT NOWAIT.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 3rd Floor| [EMAIL P
On 5/18/07, Chris Hoover <[EMAIL PROTECTED]> wrote:
Are there any others?
The main three for PostgreSQL training I know of are:
- EnterpriseDB
- Command Prompt
- Big Nerd Ranch
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation
On 5/18/07, Daniel Cristian Cruz <[EMAIL PROTECTED]> wrote:
Oops... INSERT or DELETE... :)
Heh, yeah... doh!
And remember that if using TRUNCATE, it will not run your trigger and
you will need to reset the counter manually.
Correct.
--
Jonah H. Harris, Software Architect |
If you just need
*reasonable* guesstimates, use reltuples in pg_class after an analyze.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 3rd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830
table, you can't.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 3rd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
---
-
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
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corpo
it's primarily for the buffer cache
and some shared variables.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 3rd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterpr
et them into 8.3.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
---(
h currently exists at http://gorda.di.uminho.pt/community/pgsqlhooks/
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enter
ifficult
to decompile. I've never used obfuscation because I know how easy it
is to hack one of the C or Java compilers to make the code much more
readable and understandable. Just my 2 cents... but if someone wants
to add obfuscation functionality to PL/pgSQL, by all means go for it.
--
On 7/4/06, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
On 7/4/06, Aaron Bono <[EMAIL PROTECTED]> wrote:
> I don't see how PostgreSQL being open source will stop obfuscation of the
> PL/pgSQL from being possible.
Oh, and I forgot to add, obfuscation is lame and doesn'
rsion (refusing to give them the actual source
code). I had to reverse engineer his algorithm with nothing but
wrapped code.
Just remember, if you had the source code to Oracle, the wrap utility
would be pretty much worthless as you could easily do the same thing
as PL/pgSQL and PostgreSQL.
't actually stop someone from reverse engineering it quite
easily as the source code to PL/pgSQL itself is readily available.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTE
a view to hide the original
table's details. As for hiding pg_catalog... I believe you could
create a rule on it.
Never tried to hide something this extensively... and don't really
understand a practical reason for doing so. Remember, security
through obscurity is flawed from the get
On 6/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I pulled down the oralink contrib module from the pg foundry
but it has no docs. Anyone know of ant docs/help/etc ... ?
Nope... is it even maintained?
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corpo
Not to
explicitly plug EnterpriseDB here, but we have a native OCI-based
connector for PostgreSQL which is quite a bit faster than dbi-link if
speed is what you need.
dbi-link:
http://pgfoundry.org/projects/dbi-link/
EnterpriseDB Release 2 Beta 3:
http://www.enterprisedb.com/products/download.do
--
J
I agree.
(sorry again Tom... dang GMAIL should default reply to all g!)
On 11/14/05, Tom Lane <[EMAIL PROTECTED]> wrote:
Rod Taylor <[EMAIL PROTECTED]> writes:> On Mon, 2005-11-14 at 23:02 -0500, Tom Lane wrote:
>> There's something in what you say. We'd have to rename pg_clog as well,>>
42 matches
Mail list logo
