Data warehousing using postgresql is it possible ?
Answer is yes, it is possible.
Postgresql has always been considered as not suitable for data
warehousing because of advanced database features present in it, like
transaction support , locking, etc.
But the fact is: We cannot decide performance
Hi,
I want a postgres client to be able to connect to a postgres sever on a
remote machine. But i'm not able to make it work. Assume both the machines
are on a LAN 10.0.0.* .Following available advice, this is what i did:
-- In pg_hba.conf, i added the line
host all all 10.0.0.1/24 trust
--
Hello,
I think you make mistake writing "listen_addresses = 10.0.0.*". I doubt
it can be done like this... Try "listen_addresses = '*'" first. Also
see, that addresses are in form '10.0.0.1' and not 10.0.0.1. (use ' )
If this doesn't help try telneting server (port 5432) from client
mashine. M
Hi
I'd like to know how the binary installation I have has been
originally built - in the meaning of ./configure params.
Is there a way to check this?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/
Hi,
The Postgresql configuration files can be kept elsewhere than the data
directory, as is described in the section about "File Locations."
(18.2 of as of 8.4)[1]
The documentation here basically mentions two ways of doing this.
First you can start Postgresql with the -D option to pg_ctl point
wstrzalka writes:
>I'd like to know how the binary installation I have has been
> originally built - in the meaning of ./configure params.
>Is there a way to check this?
Run pg_config
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql
Ludo Smissaert writes:
> Both methods works fine on server startup, but the first method gives
> problems when stopping the server with pg_ctl.
Yeah, pg_ctl is far too stupid to cope with such things --- it expects
that PGDATA points at the data directory. Short of teaching it to parse
the confi
Tom Lane wrote:
Ludo Smissaert writes:
Both methods works fine on server startup, but the first method gives
problems when stopping the server with pg_ctl.
Yeah, pg_ctl is far too stupid to cope with such things --- it expects
that PGDATA points at the data directory. Short of teaching it to
On 2 Lis, 16:04, t...@sss.pgh.pa.us (Tom Lane) wrote:
> wstrzalka writes:
> > I'd like to know how the binary installation I have has been
> > originally built - in the meaning of ./configure params.
> > Is there a way to check this?
>
> Run pg_config
>
> regards, tom
>>> Run pg_config
>> There is no pg_config in the binary version I use (yum version of 8.3
>> from PGDG)
>It might be in the -devel sub-RPM.
>regards, tom lane
Thank you. This is what I need.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make c
2009/11/2 Shruthi A :
> Hi,
>
> I want a postgres client to be able to connect to a postgres sever on a
> remote machine. But i'm not able to make it work. Assume both the machines
> are on a LAN 10.0.0.* .Following available advice, this is what i did:
>
> -- In pg_hba.conf, i added the line
> h
hostall all
10.0.0.1/24 trust
>> host all all trust
-- In postgresql.conf, i added the line
listen_addresses =
10.0.0.*
>> listen_address = *
& then restart the server.
--
Thanks
Sam
--- On Mon, 2/11/09, Shruthi A wrote:
From: Shruthi A
Subject: [
Hi,
I have a trouble in creating user and database in postgres. whenever I
create user or databases in capital letters, the names are always
converted into names in lower case letter. what's wrong with it?
Thanks
Dong
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make ch
You need to put double-quotes (") around your username, db name etc. -
otherwise everything is reduced to lower case.
Lewis
don...@caltech.edu wrote:
Hi,
I have a trouble in creating user and database in postgres. whenever I
create user or databases in capital letters, the names are always
c
2009/11/2 :
> Hi,
>
> I have a trouble in creating user and database in postgres. whenever I
> create user or databases in capital letters, the names are always
> converted into names in lower case letter. what's wrong with it?
> Thanks
>
> Dong
Try add ""
CREATE USER "PepeArgento";
Does vacuumdb have knowledge of a VACUUM that was done on a table in
the prior run and skip it the next time (assuming the table does not
change) ? If not.is autovacuum smart enough to figure that out ?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your su
Anj Adu escribió:
> Does vacuumdb have knowledge of a VACUUM that was done on a table in
> the prior run and skip it the next time (assuming the table does not
> change) ?
No.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt,
How about if using autovacuum daemon instead?
Regards,
Husam
-Original Message-
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Alvaro Herrera
Sent: Monday, November 02, 2009 3:00 PM
To: Anj Adu
Cc: pgsql-admin@postgresql.org
Subject
Tomeh, Husam escribió:
> How about if using autovacuum daemon instead?
Autovacuum only processes tables that need vacuuming, per the configured
parameters, so yes, it skips tables that were "recently" processed
(where "recently" is defined by said parameters and operations).
--
Alvaro Herrera
Dear Friends,
I really need help for my problem, 7 days ago Postgresql service fails
to start and i have no backup ! (OS: Windows XP Pro). I tried googling
everywhere but didn't find any solution.
I had tried to start the service manually from control panel, it
started for about 5 seconds
And autovacuum will reset the XID counter even if it skips tables
right? Just wanted to confirm before enabling autovacuum.
Thanks
Sriram
On Mon, Nov 2, 2009 at 5:39 PM, Alvaro Herrera
wrote:
> Tomeh, Husam escribió:
>> How about if using autovacuum daemon instead?
>
> Autovacuum only processes
Anj Adu escribió:
> And autovacuum will reset the XID counter even if it skips tables
> right? Just wanted to confirm before enabling autovacuum.
On 8.2 and up, yes.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Developm
Oh..ok..then I guess I have to stick with vacuumdb -a (We are running 8.1.X )
Thank you
On Mon, Nov 2, 2009 at 6:52 PM, Alvaro Herrera
wrote:
> Anj Adu escribió:
>> And autovacuum will reset the XID counter even if it skips tables
>> right? Just wanted to confirm before enabling autovacuum.
>
>
Hengky Lie writes:
> 2009-11-02 10:13:35 FATAL: could not access status of transaction
> 139856778
> 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085"
> at offset 98304: Permission denied.
You need to fix that "Permission denied" problem. Either the file
really is marked
>> 2009-11-02 10:13:35 FATAL: could not access status of
transaction 139856778
2009-11-02 10:13:35 DETAIL: Could
not read from file "pg_clog/0085" at offset 98304: Permission
denied.
I faced this error before a week only. Fortunately
we have a valid backup and we restored the file (
What exactly file pg_clog/0085 exactly is ? Thank you for any advice.
Now i'm trying to check file permission and antivirus.
On Nov 3, 2009, at 2:48 PM, Sam Jas wrote:
>> 2009-11-02 10:13:35 FATAL: could not access status of
transaction 139856778
2009-11-02 10:13:35 DETAIL: Could not re
26 matches
Mail list logo
