Hi,
I am trying to measure startup time of postmaster. Say I have postmaster
running on -D /tmp/d1 and would like to restart it on -D /tmp/d2.
If I just say
time pg_ctl restart -D /tmp/d2
it will not produce an accurate result because pg_ctl will start postmaster
in the background and return imme
testing...am I being copied to the list
Medi
sql(1)...
Cheers for now
Medi
On 8/14/07, Decibel! <[EMAIL PROTECTED]> wrote:
>
> On Mon, Aug 13, 2007 at 04:05:37PM -0700, Medi Montaseri wrote:
> > Hi,
> >
> > I am trying to measure startup time of postmaster. Say I have postmaster
>
> Why?
>
> > runnin
Hi,
I am looking for some suggestions to optimize the following
problem/solution.
Given two nodes A and B (two computers) in a active-passive mode where A is
running PG engine, and B is simply standing by, and a common storage
(twin tailed) ( or from pg_ctl point of view -D /common/data ), I a
<[EMAIL PROTECTED]> wrote:
>
> Hannes Dorbath wrote:
> > On 15.08.2007 21:30, Medi Montaseri wrote:
> >> I am looking for some suggestions to optimize the following
> >> problem/solution.
> >>
> >> Given two nodes A and B (two computers) in
Hi,
I am having difficulty compiling my postgresql 7.2.3 on a CentOS 5.
The same code works on our build machine which is running RedHat 7.2.
I have checked many of the configure(1) output with no major diff. Capturing
the output of make reveals a silly problem which I am failing to find the
roo
explain why the same makefile
works on previous OS releases, but that is another story and there many such
stories in a day of software engineer.
Cheers for now
Medi
On 8/17/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> "Medi Montaseri" <[EMAIL PROTECTED]> writes
You can think of a database as a filesystem as well. That is do some
processing, store the result in temp table, do some more, etc,etc then merge
and process temp tables to arrive at some result.
Just as in the case of filesystem, if you are operating in a concurrent
evironment, you need to fence
learning I perform 9 calls.
>
> Giu
>
> - Original Message
> Da: Scott Marlowe <[EMAIL PROTECTED]>
> To: Medi Montaseri <[EMAIL PROTECTED]>
> Cc: pgsql-admin@postgresql.org
> Oggetto: Re: [ADMIN] how to
In other words, are you sure you want to use 7.1 which is about 5 years old
?
Also note that there are binary versions for various platforms, ready to be
used.
Cheers
Medi
On 8/20/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kuriakose, Cin
Hi,
I have finally convinced my manager to "consider" the idea of migrating from
7.2 to 8.2. Obviously he needs an ROI (Return Of Investment) analysis (in a
technical sense).
So, I am wondering if anyone has worked on a similar project where you had
to go thru the release notes and bug fixes to c
What can I sayat least he is willing to listen now...thanks guys...
This is an excellent start...
Cheers everyone
Medi
On 8/21/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Medi Montaseri wrote:
> > Hi,
>
everyone.
Medi
On 8/21/07, Chris Browne <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] ("Medi Montaseri") writes:
> > I have finally convinced my manager to "consider" the idea of
> > migrating from 7.2 to 8.2. Obviously he needs an ROI (Return Of
> >
Just dont get into the habbit of moving db files around like too
muchfilesystems will spead your files all over the place and your
database will slow down
Medi
On 8/23/07, Campbell, Lance <[EMAIL PROTECTED]> wrote:
>
> Tom,
>
>
> It is nice to know that you can actually move the database
Another view is...by the time you figure out all these virtualization
solutions you can buy a used box for less than $100 (no monitor needed) and
focus on the real test. By the way, in any HA one issue will be the IP
takeover on the surviving node. Under the IP will be the Mac address of the
previ
The 3.4G per process seems too un-realistic. Here is a simple way to isolate
or narrow the scope of the problem at hand.
Bring the server up, go to the run level that you run PG, but stop PG, now
measure your memory consumption. This is your baseline.
Now start PG, but no connection, just idle, me
e for pg copy, or
just use DBI to insert it into the PG. Which is basically an ETL (Extract,
Transform, Load). I know insert is slower, but the point was to show a
general way that will always for.
Cheers
Medi Montaseri
On 8/28/07, Chris Hoover <[EMAIL PROTECTED]> wrote:
>
> I need so
I was under the impression that recent modern databases, like PG, allow you
to transfer control to an out-of-system (system being the DB engine) module
(shared lib, dll). That is while triggers transfer control within the
system, now mechanisms exists that allow you to go outside of the system. In
I see...thank you for the clarification...one more question...
How does PG protects itself from a run-away code (eg an endless loop) ? In
other words, does PG run the "untrusted" code in a seperate process?
Thanks
Medi
On 8/29/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> &q
PG maintains user passwd within itself in a table called pg_shadow.
But based on the error message, it seems like you are having problem
connecting to the server.
Try accessing PG from command line with something like psql(1) as in
psql -U proot -d databaseName
and see what error message do you g
Ok...next step is to try to connect remotely from the trusted psql(1) again,
as in
psql -U proot -d databaseName -h hostname -p portNumber
If you can connect, then your listner configuration is working ok (per other
caller's comment). In which case you focus on the application.
Cheers
Medi
On 9
Or ... ask the application not the OS
psql> select version() ;
Cheers
Medi
On 10/29/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Leaving aside the question of why one might want to do this, Unix 101
> should show you many ways to do it. For example,
>
> sed -n -e 's/.*PG_VERSION /PG
But theoretically speaking, 32 or 64-bit ness of the application (ie the
postmaster server) should not influence the data types offered by a
particular DB version. That is the semantics of data types and cpu-arch
(register width, big endian, little endian, sparc, mips, x86), etc ) offered
by a part
I agree with you practical pointsI qualified my comments by
sayingtheoretically speaking
Cheers
Medi
On Nov 26, 2007 8:01 AM, Chris Browne <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ("Medi Montaseri") writes:
> > But theoretically speaking, 32 or 64-bi
Hi,
I am configuring a PG 8.1.9 on CentOS 5. I am seeing some anomalies and
would like you feedback.
I have defined a new PGDATA=/qmsvol/pg_8.1.9/data, ran initdb -D
/qmsvol/pg_8.1.9/data successfully and can start the engine with pg_ctl -D
$PGDATA.
I have also populated /etc/sysconfig/pgsql/post
Thanks Tom..that did the magic
Would I allow PG to start from any -D place by saying
semange fcontext -a -t postgresql_db_t "/qmsvol(/.*)?"
Thanks
Medi
On Nov 26, 2007 7:48 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Medi Montaseri" <[EMAIL PROTECTED]> wr
Hi,
I know this is not exactly admin related, but ... it is simple enough to be
even fun
>From a performance point of view, is it better to use OR as in
SELECT expr FROM expr WHERE col=this OR col=that OR col=theOther
Or to use a range of values as in
SELECT expr FROM expr WHERE col in ( val1, va
36 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, 12 Dec 2007 14:25:16 -0800
> "Medi Montaseri" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I know this is not exactly admin related
On Dec 12, 2007 5:03 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> > --- On Wed, 12/12/07, Medi Montaseri <[EMAIL PROTECTED]> wrote:
> >> based on your report, run time of OR is 0.275 ms and IN is
> >>
PostgreSQL does not support SYNOSYM or ALIAS. Synonym is a non SQL 2003
feature implemented by Microsoft SQL 2005 (I think). While it does provide
an interesting abstraction, but due to lack of relational integrity, it can
be considered a risk.
That is, you can create a synonym, advertise it to yo
Hi,
I was wondering if you could critique the following DB application
development process.
Given a production DB and a Dev DB:
1- Develope schema and code on Dev including test data which will impact
sequences, etc
2- Dump the schema only (not the data) from Dev and restore it into the
productio
The usual trap in cron usage is the fact that crontab commands are executed
in a cleanroom environment, ie no environment variable is used/inherited, so
PATH, HOME, PGDATA, etc are not set/available when the command is launched.
You can set vars or be very explicit in your script including DB name
Hi,
I am faced with a database disapperance and seeking some explanations
outside of gremlins.
I had a database running at
cat /etc/sysconfig/pgsl/postmaster
PGDATA=/qmsvol/pg_8.1.9/data
PGLOG=/var/log/pgsql/pgstartup.log
Where /qmsvol is an iSCSI block device
A couple of days ago, my server was
Lane <[EMAIL PROTECTED]> wrote:
> Steve Holdoway <[EMAIL PROTECTED]> writes:
> > "Medi Montaseri" <[EMAIL PROTECTED]> wrote:
> >> I think the following happend...
> >> Since my PGDATA was on an iSCSI device, by the time
> /etc/rc3.d/S64post
did you kill -hup syslogd after you changed syslog.conf
On Thu, May 29, 2008 at 11:04 PM, Achilleas Mantzios <
[EMAIL PROTECTED]> wrote:
> Στις Friday 30 May 2008 07:35:19 ο/η kevin kempter έγραψε:
> > Hi list;
> >
> > I'm trying to get postgres & syslog to get along with no luck. I'm
> > running
You can write a program in say Perl and use "create user bob with
.options encrypted password x valid until xxx " which is pretty
much what createuser(1) does.
Cheers
Medi
On Tue, Jun 3, 2008 at 12:54 AM, Илья Скорик <[EMAIL PROTECTED]> wrote:
> Dear community, help please.
>
> I nee
On Tue, Jun 10, 2008 at 12:49 PM, Scott Marlowe <[EMAIL PROTECTED]>
wrote:
> On Wed, May 28, 2008 at 11:14 PM, Medi Montaseri <[EMAIL PROTECTED]>
> wrote:
> > Yes, this type of presumptuous behavior to wipe out a production database
> > based on a few checks is too
37 matches
Mail list logo
