Simon | 1 Jul 14:54 2007
Picon

--with-ldap prerequisites

Hi,

I am trying to compile 8.2.4 on solaris 10.

I would like to use ldap authentication so I specified --with-ldap however I get the following error.

Undefined                       first referenced
 symbol                             in file
ldap_start_tls_s                    libpq/SUBSYS.o


I assume this is because I haven't installed the op enldap libraries?

Is there any way to use ldap authentication without installing open ldap?

Could I use the SUNWlldap package?

I want to eventually authenticate against an active directory domain.

Thanks,
Simon

Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
Joe Barwell | 2 Jul 03:23 2007
Picon

Re: initdb problem

Hello people,

My initdb problem has been solved (PostgreSQL 8.2.4, Mac OS
X 10.3.9). I thought I would post a brief summary, but first
I'd like to thank everyone on this list who so kindly and
generously made suggestions. I'd particularly like to thank
Sean Dooley <srd1 <at> st-andrews.ac.uk>, who assisted me greatly
offlist, and whose suggestions eventually provided the
solution.

Earlier in this thread it was suggested that another, older
version of postgres may already be running on my machine,
but I believe that not to have been the case. One of Sean's
suggestions was to run the following in Terminal:

ps -aux | grep post

which returned nothing other than itself, whereas run
earlier today it shows:

postgres   686   0.0  0.2    40484   1284 std- S    Fri07AM 
 0:03.53 /opt/local/lib/postgresql82/bi
postgres   689   0.0  0.1    40484    484  ??  Ss   Fri07AM 
 1:00.27 postgres: writer process
postgres   690   0.0  0.0    36460    168  ??  Ss   Fri07AM 
 0:07.16 postgres: stats collector proc
postgres  1228   0.0  0.4    41092   2804  ??  Ss    7:57AM 
 0:00.46 postgres: acorn testdb 127.0.0
postgres  1230   0.0  0.4    41092   2428  ??  Ss    7:58AM 
 0:00.18 postgres: acorn postgres 127.0
acorn     1255   0.0  0.0     8860    120 std  R+    9:56AM 
 0:00.00 grep post

Postgres is also now clearly visible in Activity Monitor
(five times, as above).

What worked for me was the following:

At Sean's suggestion I uninstalled the Postgres 8.2.4 I'd
got from the universal binary installer, and instead used
macports
<http://svn.macosforge.org/repository/macports/downloads/>
(NB, requires apple developer tools be already installed) to
install postgres:

sudo port selfupdate
sudo port install postgresql82
sudo port install postgresql82-doc
sudo port install postgresql82-server

The latter installation handily advised (in Terminal)
editing the file /etc/hostconfig by adding the line:

POSTGRESQL82-SERVER=-YES-

to make postgres server run on startup.

I then ran through the following:

sudo mkdir -p /opt/local/var/db/postgresql82/defaultdb
sudo chown postgres:postgres
/opt/local/var/db/postgresql82/defaultdb
sudo su postgres -c '/opt/local/lib/postgresql82/bin/initdb
-D /opt/local/var/db/postgresql82/defaultdb'

which created the cluster. At the end of that Terminal
advised using:

/opt/local/lib/postgresql82/bin/postgres -D
/opt/local/var/db/postgresql82/defaultdb
or
/opt/local/lib/postgresql82/bin/pg_ctl -D
/opt/local/var/db/postgresql82/defaultdb -l logfile start

to start the database server, but what actually worked was
the following:

sudo su postgres -c '/opt/local/lib/postgresql82/bin/pg_ctl
-D /opt/local/var/db/postgresql82/defaultdb start'

(this fed the log back to Terminal). Beware when trying to
specify a logfile location that one chooses a directory to
which the postgres user can write--i.e. it may be simpler to
use a full path, such as:

sudo su postgres -c '/opt/local/lib/postgresql82/bin/pg_ctl
-D /opt/local/var/db/postgresql82/defaultdb -l
/opt/local/var/db/postgresql82/defaultdb/logfile start'

as otherwise the logfile will default to creation in the
current directory, for which postgres may not have
permissions.

Now that I have postgres running I think it best if I soon
leave this forum, and join another more suited to the
no-doubt many other very basic problems and questions I
shall encounter. Thanks again.

Cheers!

Joe

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Simon Riggs | 2 Jul 11:35 2007

Re: missing history file

On Fri, 2007-06-29 at 10:52 -0400, Tom Lane wrote:
> "Simon Riggs" <simon <at> 2ndquadrant.com> writes:
> > Just ignore 00000001. Recovery will work fine even if absent. Don't
> > ignore all history files though, just that one. Hmmm, come to think of
> > it, why is it requesting it at all? We should just skip that request.
> 
> No, because then people would misdesign their recovery scripts to not
> be able to deal with not finding a history file.  As things are, they
> will certainly be exposed to that case in any testing they do.  If we
> optimize this call away, then they won't see the case until they're in
> very deep doo-doo.

Main reason for suggesting this is that there is already code to
optimize the call away in one place, but not in another, which seems
strange either way.

--

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Yuan HOng | 2 Jul 14:41 2007
Picon

(unknown)

Hi, list,

Can you give me some suggestions as to what replication solution best
suits my situation:

I have an online product sales applicaiton, which is split between two
sites. The web front-end sits at the ISP's data center and accepts
customer order. The server in the office handles the product lisitng,
order processing and also takes ordres on telephone. The two sites are
linked over Internet using ADSL, i.e. not high bandwidth. Due to high
Internet cost here, it would be infeasible to move the two servers
together.

For the production information tables, they will be solely maintained
inhouse, and will be synced to the web server. I have been using
Slony-I for this. But for ordre and customer information, since both
sites shall update these tables, and the link is over a WAN, it seems
the most appropriate replication solution would be a multi-master,
asynchronous solution.

I have done a quick research on the current PostgreSQL replication
solutions: Slony-I, PGPool(-I and -II), PGCluster, and none of them
seems to fit exactly my situaiton:

Slony-I is only single master. The only possible way to use it would
be to use a separate table for order on web server and replicate it
back to inhouse server. But then I have two tables for order, which
will make the applicate much complicated.

PGPool is used primarily for connection poolling. It can do
synchronous replication on database level by sending the SQL commands
to 2 servers. But since the WAN connection is not stable, if the
connection is down for a while, the replication will be broken and I
don't think PGPool can resync the two databases automatically.

PGCluster is similar to PGPool in being a synchronous replication
solution. I thinks it would only be useful for a LAN situation. Over a
WAN, if the link is broken, I think it would also be impossible for it
to resume replication. Also, it seems I can only replicate the whole
database, not the selected tables.

Finding no suitable soluiton for my case, I am wondering whether I
have made a mistake in my database design. Havent' others experienced
similiar situation as I do? Or do I have some misunderstanding of the
capabilities of the existing solutions? Am I overlooking something?

It seems Slony-II would be quite promising, but I can't wait that
long. What is the best choice for me now?

Thanks for helping!

--

-- 
Hong Yuan

大管家网上建材超市
装修装潢建材一站式购物
http://www.homemaster.cn

---------------------------(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
Ritu Khetan | 2 Jul 15:10 2007

pg_hba.conf issue


Hi friends,

We have a product with Postgres 8.1 integrated for installations on
Windows. The standard pg_hba.conf configuration going in the package is

# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD

# IPv4 local connections:
host    all         all         127.0.0.1/32          trust
# IPv6 local connections:
#host    all         all         ::1/128               trust
#host    all         all         172.21.42.121/24               trust
host    all         all         172.21.51.56/24               trust

While this works at most of the locations, we have a peculiar error coming
up at 2-3 locations. The error reads:

no pg_hba.conf entry for host "::1" , user "crisil" , database "crisil" ,
SSL off "

Can someone give any clue on why could this be coming up? We do not intend
to use SSL either. Our analysis shows this problem gets resolved if the
entry for ::1/128 is uncommented but we would like to understand in which
scenario is this entry needed.

Regards,
Ritu
Disclaimer : 
This message (including any attachments) contains confidential information. If you are not the intended
recipient, please delete the message (including any attachments) from your system without using,
transmitting or storing it. Please also immediately inform the sender. E-mails are not secure and may
suffer from errors, viruses, unauthorized interceptions / amendments. CRISIL and its subsidiaries do
not accept any liability for loss or damage caused by this e-mail and may monitor e-mail traffic.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Jayakumar_Mukundaraju | 2 Jul 15:51 2007

pg_hba.conf issue

Hi friends,

I am Jayakumar and  new to PostgreSQL world. I am using PostgreSQL 8.1.3
in Windows 2000 machine.

My problem is, I am unable to connect to PostgreSQL server from another
machine's psql client.

My system IP is 172.16.84.76, and client machine IP is 172.16.85.243.

I can connect to the PostgreSQL server with " psql -Uroot
-h172.16.84.76"
from same system(172.16.84.76)

If I give the above command from 172.16.85.243, results

D:\\Program Files\PostgreSQL\8.1\bin>psql -Uroot - h172.16.84.76
psql: could not connect to server: Connection refused (0x0000274D/10061)
        Is the server running on host "172.16.84.76" and accepting
        TCP/IP connections on port 5432?

I don't know how to do this in windows.

here pg_hba.conf entries follows
*************************************
host    all         all         172.16.84.76/32         md5
host    all         all         172.16.85.243/32            md5

here postgre.conf entry follows
***********************************
#-----------------------------------------------------------------------
----
# CONNECTIONS AND AUTHENTICATION
#-----------------------------------------------------------------------
----

# - Connection Settings -

listen_addresses = '*'        # what IP address(es) to listen on;
                    # comma-separated list of addresses;
                    # defaults to 'localhost', '*' = all
port = 5432
max_connections = 100
# note: increasing max_connections costs ~400 bytes of shared memory per
# connection slot, plus lock space (see max_locks_per_transaction).  You
# might also need to raise shared_buffers to support more connections.

superuser_reserved_connections = 10

#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777        # octal
#bonjour_name = ''            # defaults to the computer name

# - Security & Authentication -

authentication_timeout = 150        # 1-600, in seconds

#ssl = on

#password_encryption = on
#db_user_namespace = off

# Kerberos
#krb_server_keyfile = ''
#krb_srvname = 'postgres'
#krb_server_hostname = ''        # empty string matches any keytab entry
#krb_caseins_users = off

# - TCP Keepalives -
# see 'man 7 tcp' for details

#tcp_keepalives_idle = 0        # TCP_KEEPIDLE, in seconds;
                    # 0 selects the system default
#tcp_keepalives_interval = 0        # TCP_KEEPINTVL, in seconds;
                    # 0 selects the system default
#tcp_keepalives_count = 0        # TCP_KEEPCNT;
                    # 0 selects the system default

Please find my problem, give me the solution...

Thanks & Regards
Jayakumar M

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may
contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others
or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY
PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all
copies; your cooperation in this regard is appreciated.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Jessica Richard | 2 Jul 16:23 2007
Picon

select * from a 3M-row table very slow

Is there anything that can make this faster? Is there any memory config (postgres and OS) that can be tuned? it came back very quick under Informix.
Thanks.

Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.

Re: select * from a 3M-row table very slow

Hi !
Tell us your hardware and software configurations.
[]s

> ----- Original Message -----
> From: "Jessica Richard" <rjessil <at> yahoo.com>
> To: pgsql-admin <at> postgresql.org
> Subject: [ADMIN] select * from a 3M-row table very slow
> Date: Mon, 2 Jul 2007 07:23:29 -0700 (PDT)
> 
> 
> Is there anything that can make this faster? Is there any memory 
> config (postgres and OS) that can be tuned? it came back very quick 
> under Informix.
> Thanks.
> 
> 
> ---------------------------------
> Looking for earth-friendly autos?
>   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.

>

=

--

-- 
Powered by Outblaze

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Tom Lane | 2 Jul 17:38 2007
Picon

Re: pg_hba.conf issue

Ritu Khetan <RKhetan <at> crisil.com> writes:
> # IPv4 local connections:
> host    all         all         127.0.0.1/32          trust
> # IPv6 local connections:
> #host    all         all         ::1/128               trust
> #host    all         all         172.21.42.121/24               trust
> host    all         all         172.21.51.56/24               trust

> While this works at most of the locations, we have a peculiar error coming
> up at 2-3 locations. The error reads:

> no pg_hba.conf entry for host "::1" , user "crisil" , database "crisil" ,
> SSL off "

No surprise: you have the IPv6 line commented out.  Dunno why these
particular boxes are preferring IPv6 to IPv4, maybe something different
about the local DNS environment?  Anyway, there is no point in refusing
to serve ::1/128 if you're accepting 127.0.0.1.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

André José Guergolet | 2 Jul 18:04 2007
Picon

Re: select * from a 3M-row table very slow

Please, send your query, table definition and indexes and the execution plan.

-----Original Message-----
From: pgsql-admin-owner <at> postgresql.org [mailto:pgsql-admin-owner <at> postgresql.org] On Behalf Of
Daniel Alvão Carvalho Júnior
Sent: segunda-feira, 2 de julho de 2007 11:31
To: pgsql-admin <at> postgresql.org
Subject: Re: [ADMIN] select * from a 3M-row table very slow

Hi !
Tell us your hardware and software configurations.
[]s

> ----- Original Message -----
> From: "Jessica Richard" <rjessil <at> yahoo.com>
> To: pgsql-admin <at> postgresql.org
> Subject: [ADMIN] select * from a 3M-row table very slow
> Date: Mon, 2 Jul 2007 07:23:29 -0700 (PDT)
> 
> 
> Is there anything that can make this faster? Is there any memory 
> config (postgres and OS) that can be tuned? it came back very quick 
> under Informix.
> Thanks.
> 
> 
> ---------------------------------
> Looking for earth-friendly autos?
>   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.

>

=

--
Powered by Outblaze

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq


Gmane