[GENERAL] Error - could not get socket error status: Invalid argument
Hi , I am working on hpux itanium platform I am using postgres 8.4.0 version and have compiled 64bit libpq library. While conneting I am getting error " could not get socket error status: Invalid argument" can someone help here? Why I am getting this error while connecting to database. Regards Rajaram J We all make mistakes, but it's our responses to said mistakes that separate true leaders from the rest of the pack.
[GENERAL] New PostgreSQL Committers
On behalf of the core team, I'm pleased to announce that the PostgreSQL Project has expanded it's team of "committers", those people who are able to make direct changes to the PostgreSQL source code respository. As the project is extremely conservative about any changes made to the source code to minimise the risk of introducing any bugs, commit access is only given to contributors who have consistently shown they work to a very high standard and have shown commitment to the project. The new committers are: Robert Haas: Robert developed the commitfest.postgresql.org website which is used to manage the process by which features are added to PostgreSQL. He has twice acted as commitfest manager, and submitted numerous patches such as join removal, auto-generation of headers & bki files and the TRUNCATE privilege. Simon Riggs: Simon is well know for working on large enterprise features for PostgreSQL, including Point In Time Recovery and partitioning. Simon is currently working on allowing PITR slave servers to be used for read-only queries. Greg Stark: Greg has worked on low-level features in PostgreSQL, including asynchronous pre-fetching of data and packed variable length data types. Greg was also responsible for the CREATE INDEX CONCURRENTLY feature. ITAGAKI Takahiro: ITAGAKI-san has worked on countless patches for PostgreSQL, both fixing bugs and writing new features, recently including WHEN clauses for triggers, a buffer usage feature for EXPLAIN and a new implementation of VACUUM FULL. Congratulations! -- Dave Page PostgreSQL Core Team -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [HACKERS] [GENERAL] Installing PL/pgSQL by default
Tom Lane writes: > Right, just like every other thing that's pre-installed. If a > particular installation wishes to let individual DB owners control this, > the superuser can drop plpgsql from template1. It's not apparent to me > why we need to allow non-superusers to override the project's decisions > about what should be installed by default. I guess it boils down to being nice to hosting platforms, where they will want to give as much power as can be given to database owners without having those hosted people be superusers. So should the decision to remove plpgsql be on the hosting platform hands or the hosted database owner? Regards, -- dim -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Array comparison & prefix search
On Sat, Dec 05, 2009 at 09:54:58AM -0500, Merlin Moncure wrote: > GIN is a pretty heavy price to pay for something that should be btree > indexable. Also note he is using a multi column index with array as > second column...that would be pretty awkward with GIN. Yup, sounds as though it's not going to work here. I was mainly suggesting it as it's working now, as opposed to something that could/should be made to work. > Normalizing the data loses the nice property of being able to order > the entire structure using a single index. He's using the array as if > it was a string...it's basically an optimization. Hum, not sure why this didn't come up already: what about having an index on (type,(array_to_string(ident,'##')) and relying on the already existing optimizations for string prefixes. Not sure what sort of values can be used in "ident", but it could work. -- Sam http://samason.me.uk/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] What packages I need to install to get Postgres working
On Sun, Dec 06, 2009 at 02:21:09PM -0800, John R Pierce wrote: > yourusername $ sudo su - postgres > postgres $ psql Somebody pointed out to me on this list that you don't need su for that. The following is equivalent: sudo -u postgres psql Also, because it's all one line it plays nicely when running from history. -- Sam http://samason.me.uk/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Error_startup postgresql server
Hi,
I'm using Postgresql 8.7.3 on Debian. I was trying to launch the postgresql
server to create a simple user and a database, but I've got this output:
--
jc:/usr/local/pgsql/data1# su - postgres
postg...@jc:~$ /usr/local/pgsql/bin/pg_ctl start -l logfile -D
/usr/local/pgsql/data1/data/
server starting
postg...@jc:~$ /usr/local/pgsql/bin/createuser radius --no-superuser
--no-createdb --no-createrole -P
Enter password for new role:
Enter it again:
createuser: could not connect to database postgres: could not connect to
server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
--
I've search the web and seen some people saying to uncomment a line in the
postgresql.conf file ("tcpip_socket = true") but I don't have this line! I'm
not understanding what's wrong, why can't I create an user, supposedly the
server is running..
Can someone tell me what am I doing wrong?
Thank you,
Joana Camacho.
Re: [GENERAL] Error_startup postgresql server
On 07/12/2009 13:54, Joana Camacho wrote:
> Hi,
>
> I'm using Postgresql 8.7.3 on Debian. I was trying to launch the postgresql
> server to create a simple user and a database, but I've got this output:
>
> --
> jc:/usr/local/pgsql/data1# su - postgres
> postg...@jc:~$ /usr/local/pgsql/bin/pg_ctl start -l logfile -D
> /usr/local/pgsql/data1/data/
> server starting
> postg...@jc:~$ /usr/local/pgsql/bin/createuser radius --no-superuser
> --no-createdb --no-createrole -P
> Enter password for new role:
> Enter it again:
> createuser: could not connect to database postgres: could not connect to
> server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
> --
>
> I've search the web and seen some people saying to uncomment a line in the
> postgresql.conf file ("tcpip_socket = true") but I don't have this line! I'm
> not understanding what's wrong, why can't I create an user, supposedly the
> server is running..
I think that should be
listen_addresses = *
By default the server listens only on local Unix sockets - you have to
uncomment the above line to have it listen on a TCP/IP address/port.
Setting the option to "*" has it listen on port 5432 (the default port)
on all available addresses; you can restrict it to a specific address or
addresses by specifying them on this line.
Ray.
--
Raymond O'Donnell :: Galway :: Ireland
r...@iol.ie
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [HACKERS] [GENERAL] Installing PL/pgSQL by default
Dimitri Fontaine writes: > So should the decision to remove plpgsql be on the hosting platform > hands or the hosted database owner? Why not? If they really want to prohibit use of a feature the upstream project has decided should be standard, that's their privilege. The argument against seems to be basically "this should work exactly like it did before", but if that's the standard then we can never have plpgsql installed by default at all. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error_startup postgresql server
Joana Camacho wrote:
> postg...@jc:~$ /usr/local/pgsql/bin/pg_ctl start -l logfile -D
> /usr/local/pgsql/data1/data/
> server starting
> postg...@jc:~$ /usr/local/pgsql/bin/createuser radius --no-superuser
> --no-createdb --no-createrole -P
> Enter password for new role:
> Enter it again:
> createuser: could not connect to database postgres: could not connect to
> server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
> --
>
> I've search the web and seen some people saying to uncomment a line in the
> postgresql.conf file ("tcpip_socket = true") but I don't have this line! I'm
> not understanding what's wrong, why can't I create an user, supposedly the
> server is running..
tcpip_socket is for older versions, but according to the error message, the
createuser program doesn't try to connect to a TCP/IP socket so whether there
is one or not is not relevant to your immediate problem.
Maybe the postgresql server fails to start, first you want to look for errors
in 'logfile' (your -l option to pg_ctl start) about that.
Othewise you sould follow the lead of the error message and check things such
as if /tmp/.s.PGSQL.5432 exists, what are its permissions, if it doesn't
exist what is the value of the unix_socket_directory parameter in
postgresql.conf, or what port postgres is configured to listen to (also in
postgresql.conf).
If they're non-standard you need pass additional options to the createuser
command.
Best regards,
--
Daniel
PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Array comparison & prefix search
On Mon, Dec 7, 2009 at 7:01 AM, Sam Mason wrote: > On Sat, Dec 05, 2009 at 09:54:58AM -0500, Merlin Moncure wrote: >> GIN is a pretty heavy price to pay for something that should be btree >> indexable. Also note he is using a multi column index with array as >> second column...that would be pretty awkward with GIN. > > Yup, sounds as though it's not going to work here. I was mainly > suggesting it as it's working now, as opposed to something that > could/should be made to work. > >> Normalizing the data loses the nice property of being able to order >> the entire structure using a single index. He's using the array as if >> it was a string...it's basically an optimization. > > Hum, not sure why this didn't come up already: what about having an > index on (type,(array_to_string(ident,'##')) and relying on the already > existing optimizations for string prefixes. Not sure what sort of > values can be used in "ident", but it could work. hm, that's certainly an interesting idea, but I think unless you pad all the strings out you are going to run into some odd ordering issues. If it works though I think you'll have a much tighter index than the raw one over the array. merlin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error - could not get socket error status: Invalid argument
"Jayaraman, Rajaram (STSD)" writes:
> I am using postgres 8.4.0 version and have compiled 64bit libpq library.
How did you do that exactly?
> While conneting I am getting error
> " could not get socket error status: Invalid argument"
A bit of grepping shows that it failed here:
ACCEPT_TYPE_ARG3 optlen = sizeof(optval);
if (getsockopt(conn->sock, SOL_SOCKET, SO_ERROR,
(char *) &optval, &optlen) == -1)
{
appendPQExpBuffer(&conn->errorMessage,
libpq_gettext("could not get socket error status: %s\n"),
SOCK_STRERROR(SOCK_ERRNO, sebuf, sizeof(sebuf)));
The most likely bet seems to be that optlen isn't of the width the
kernel is expecting, which would imply that configure didn't choose
the type ACCEPT_TYPE_ARG3 correctly, which would imply that HP's
done something weird and unlike every other platform. Which would
not be too much of a surprise :-(. Or possibly you gave configure
some inconsistent arguments that confused it.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Query using partitioned table hangs
A re-post, since I'm really stuck on this and could use some advice on how to troubleshoot this... I have an app that was previously using a large unpartitioned table with no problems. I partitioned this table and am now experiencing intermittent hangs when inserting data into the partitioned table. The stored procedure that does the insert seems to run to completion even when it 'hangs'. There are no messages in the log file, no errors/exceptions that I'm aware of, and I'm at a loss as to what is causing this, so any help would be much appreciated. Here's the details: PostgreSQL version: 8.4 OS: Reproduced on both, RHEL 5.3 and OS X 10.5 Application: Java 1.6, using PostgreSQL 8.4 JDBC type 4 driver. The application invokes a pl/pgsql stored procedure (with autocommit set to true). This sproc does several inserts - see below for the code. This works fine with a single unpartitioned table, even for large inserts. With the table partitioned, it hangs intermittently, usually occurs within 20 - 30 minutes of running the application, after invoking the sproc ~25 times. When it hangs, it hangs indefinitely - I know because I inadvertently left it in 'hung' state for 24 hours, so it's not just slow. The last command of the sproc truncates the staging table, raw_data. The table raw_data is empty when the query is hung, which suggests that the sproc is running to completion. I tried sending a SIGHUP to the postmaster process (kill -1) while the sproc was hung, thinking it might be a thread blocked somewhere, but that had no effect. The relevant tables, queries etc are listed below: -- The parent table CREATE TABLE event ( id BIGSERIAL PRIMARY KEY, evt_time TIMESTAMP WITH TIME ZONE NOT NULL, fk_host INTEGER REFERENCES dim_host NOT NULL, fk_user INTEGER REFERENCES dim_user ); -- example of a child table: CREATE TABLE event_y2009m09 ( CONSTRAINT event_y2009m09_evt_time_check CHECK (evt_time >= '2009-09-01'::date AND evt_time < '2009-10-01'::date) ) INHERITS (event) WITH ( OIDS=FALSE ); -- Example of trigger function used CREATE OR REPLACE FUNCTION event_insert_trigger() RETURNS trigger AS $BODY$ BEGIN IF ( NEW.evt_time >= DATE '2009-08-01' AND NEW.evt_time < DATE '2009-09-01' ) THEN INSERT INTO event_y2009m08 VALUES (NEW.*); ELSIF ( NEW.evt_time >= DATE '2009-09-01' AND NEW.evt_time < DATE '2009-10-01' ) THEN INSERT INTO event_y2009m09 VALUES (NEW.*); ELSE RAISE EXCEPTION 'Date out of range.'; END IF; RETURN NULL; END; $$ LANGUAGE plpgsql; -- The sproc that hangs CREATE OR REPLACE FUNCTION normalize_data() RETURNS void AS $BODY$ DECLARE str_value text; match record; BEGIN -- Run analyze to keep statistics up to date -- raw_data contains ~60,000 records at this point ANALYZE raw_data; INSERT INTO dim_host (name_str) SELECT DISTINCT host_name FROM raw_data EXCEPT SELECT name_str FROM dim_host; ANALYZE dim_host; -- Do a few more inserts like the above -- Then copy all the records from the staging table -- Simplified for brevity - real query is a 12-way join -- All FK constraints on table event are dropped before -- we run this query. -- All appropriate partitions and triggers have been created -- in advance of running this query. INSERT INTO event (evt_time, fk_host, fk_user) SELECT r.evt_time, dim_host.id, dim_user.id FROM raw_data as r JOIN dim_host ON r.host_name = dim_host.name_str LEFT JOIN dim_user ON r.user_name = dim_user.user_name; TRUNCATE raw_data; RETURN; END; $$ LANGUAGE plpgsql; -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error_startup postgresql server
Joana Camacho writes: > I'm using Postgresql 8.7.3 on Debian. I was trying to launch the postgresql > server to create a simple user and a database, but I've got this output: Did you look into the postmaster logfile? It's not clear from this if it failed to start (if so it should have put a message in the logfile) or if it started but is not listening where createuser expects the socket to be. createuser says it expects it at "/tmp/.s.PGSQL.5432" which is the standard place on most platforms; but I think Debian prefers something under /var/run, so you could be running into a problem of having partially absorbed some Debian preferences. You could also try using ps to confirm whether the postmaster is running and if so use lsof on it to see where its socket is. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [HACKERS] New PostgreSQL Committers
On Mon, Dec 7, 2009 at 5:49 AM, Dave Page wrote: > > The new committers are: > > Robert Haas > Simon Riggs > Greg Stark > ITAGAKI Takahiro > > Congratulations! > +1 -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Add pg server to cluster
Hi there. I'm using PostgreSQL as my main database engine. Everything works. I have one server for PostgreSQL, and space on it are lowing down. I want to buy a new server and somehow connect it with first one, that PostgreSQL will use this new server's HDD. I don't want to buy new HDD for the first server, because I don't have a space in server box. So, currently PostgreSQL data are located in /var/lib/pgsql/data folder. If I connect new server, how should I connect new server's folders to this directory, so PostgreSQL can add space for its data? Or maybe it's unreal to do? Unreal to use several network folders for data? I'm new in clustering... Maybe it's possible to split up data folder (and the mount it via NFS, for example)? Thanks for patients. -- )\._.,--,'``. /, _.. \ _\ (`._ ,. `._.-(,_..'--(,_..'`-.;.' -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [HACKERS] [GENERAL] Installing PL/pgSQL by default
Tom Lane writes: > Why not? If they really want to prohibit use of a feature the upstream > project has decided should be standard, that's their privilege. Well, I guess they could also automate their database creation to fix the privileges and assign the ownership of the language to the owner of the database. Then whether or not to have plpgsql there is up to the owner. For non-hosted environments, you always want to tweak some things, like installing plpgsql in the first place. So... > The argument against seems to be basically "this should work exactly > like it did before", but if that's the standard then we can never > have plpgsql installed by default at all. Don't get me wrong, I'm all for having plpgsql installed by default. I though we were talking about how to provide that and trying to decide if having to be superuser to drop plpgsql after having created the database is blocking the way forward, knowing than installing the language only requires being database owner. Regards, -- dim -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [HACKERS] New PostgreSQL Committers
Jaime Casanova wrote: > Dave Page wrote: >> >> The new committers are: >> >> Robert Haas >> Simon Riggs >> Greg Stark >> ITAGAKI Takahiro >> >> Congratulations! >> > > +1 Outstanding! Congratulations, all! -Kevin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Help! xlog flush request is not satisfied
Hi. I just logged into a system and found this in the log when trying to start postgres. LOG: database system shutdown was interrupted; last known up at 2009-12-07 06:27:33 CET LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 15/B320AF68 LOG: record with zero length at 15/B348B9B0 LOG: redo done at 15/B348B980 LOG: last completed transaction was at log time 2009-12-07 05:54:19.655173+01 FATAL: xlog flush request 15/B37CA000 is not satisfied --- flushed only to 15/B348B9B0 CONTEXT: writing block 0 of relation base/16386/119806_vm LOG: startup process (PID 27338) exited with exit code 1 LOG: aborting startup due to startup process failure And now I'm unsure what to do. (running postgresql 8.4.1) Any idea on what is wrong here, any suggestions on what I should do? I've found out that there is a command pg_resetxlog that some people have run in these circumstances, but I'd rather not run anthing before someone tells me what is going on. There is a backup (pg_dumpall) that is about 12 hours old that I think I could use if that is the best option. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] could not access status of transaction 825832753
I just got this error, and I don't know why I got it: 7/12/09 2:57:24 PMorg.postgresql.postgres[89]ERROR: could not access status of transaction 825832753 7/12/09 2:57:24 PMorg.postgresql.postgres[89]DETAIL: Could not open file "pg_clog/0313": No such file or directory. 7/12/09 2:57:24 PMorg.postgresql.postgres[89]STATEMENT: select u.link, u.url from link_relurl as u left join link_meta as m on (m.link = u.link) where u.url like 'http://www.somedomain.com/%' and released not in (2,4) and url not like 'http://www.somedomain.com/blah%' order by length(url) limit 200; Retrying the SQL resulted in the same error. I immediately ran pg_dump on the entire database. No errors reported. I checked the disk volume. No problems found. No console message about disk errors. SMART status is OK. I quit psql, and then restarted psql and re-entered the SQL. The statement succeeded. I did "vacuum analyze " on both the tables in the SQL statement. No errors. Both tables are quite large (around 20GBytes). I then did "select count(*) from link_relurl" and my Mac crashed hard (multilingual grey-screen asking me to hold the power button down). After reboot, "select count(*) from link_relurl" (and the other table) succeeded. pg_clog/ contains 146 files from 03F1 to 0482, so pg_clog/0313 is long gone. I've searched past messages, and found references to disk corruption and advice to rebuild the entire database. Is that still the advice? Is there anyway to check that the database is not corrupted? Is running "vacuum analyze" on a table enough to prove it is not corrupted? My details: Mac Pro 2009 Quad 2.93 with 16G of ECC RAM Snow Leopard 10.6.2 in 64bit mode, fully patched Database on RAID 0 array of SSDs Postgres 8.4.1, 64 bit, compiled from source I just installed Windows 7 in boot camp (on a different disk), and rearranged the SATA cabling. But since the problem "disappeared" on reboot I'm thinking the corruption, if any, was in RAM not on disk. Stephen
[GENERAL] freeradius postgresql sql query glitch
Hi,
I've observed an SQL logging problem with FreeRADIUS (2.x) and PostgreSQL
(8.1), on several different installations I occasionally get these errors:
Mon Dec 7 13:19:01 2009 : Error: [ourlittle_sql] Couldn't update SQL
accounting STOP record - ERROR: invalid input syntax for integer: ""
sql trace log indicates that this is the offending query:
UPDATE radacct
SET AcctStopTime = ('2009-12-07 13:19:01'::timestamp - '6'::interval),
AcctSessionTime = CASE WHEN '' = '' THEN
(EXTRACT(EPOCH FROM ('2009-12-07 13:19:01'::TIMESTAMP WITH TIME ZONE -
AcctStartTime::TIMESTAMP WITH TIME ZONE
- '6'::INTERVAL)))::BIGINT ELSE '' END,
AcctInputOctets = (('0'::bigint << 32) + '0'::bigint),
AcctOutputOctets = (('0'::bigint << 32) + '0'::bigint),
AcctTerminateCause = 'User-Request',
AcctStopDelay = 0,
FramedIPAddress = NULLIF('4.3.2.1', '')::inet,
ConnectInfo_stop = ''
WHERE AcctSessionId = '57fc9e4821466d86'
AND UserName = 'o...@user.name'
AND NASIPAddress = '1.2.3.4'
AND AcctStopTime IS NULL;
I'm using the default unchanged sql/postgresql/dialup.conf setting:
accounting_stop_query = "UPDATE ${acct_table2} \
SET AcctStopTime = ('%S'::timestamp - '%{%{Acct-Delay-Time}:-0}'::interval), \
AcctSessionTime = CASE WHEN '%{Acct-Session-Time}' = '' THEN \
(EXTRACT(EPOCH FROM ('%S'::TIMESTAMP WITH TIME ZONE -
AcctStartTime::TIMESTAMP WITH TIME ZONE \
- '%{%{Acct-Delay-Time}:-0}'::INTERVAL)))::BIGINT ELSE '%{Acct-Session-Time}'
END, \
AcctInputOctets = (('%{%{Acct-Input-Gigawords}:-0}'::bigint << 32) +
'%{%{Acct-Input-Octets}:-0}'::bigint), \
AcctOutputOctets = (('%{%{Acct-Output-Gigawords}:-0}'::bigint << 32) +
'%{%{Acct-Output-Octets}:-0}'::bigint), \
AcctTerminateCause = '%{Acct-Terminate-Cause}', \
AcctStopDelay = 0, \
FramedIPAddress = NULLIF('%{Framed-IP-Address}', '')::inet, \
ConnectInfo_stop = '%{Connect-Info}' \
WHERE AcctSessionId = '%{Acct-Session-Id}' \
AND UserName = '%{SQL-User-Name}' \
AND NASIPAddress = '%{NAS-IP-Address}' \
AND AcctStopTime IS NULL"
Looks like the code wants to use CASE to check whether %{Acct-Session-Time}
exists among the internal FreeRADIUS variables, while the return value of
the whole SQL CASE construct is supposed to be a bigint.
This is a reduced failing case:
radiustmobile=# select CASE WHEN '' = '' THEN (EXTRACT(EPOCH FROM ('2009-12-07
13:19:01'::TIMESTAMP WITH TIME ZONE - AcctStartTime::TIMESTAMP WITH TIME ZONE -
'6'::INTERVAL)))::BIGINT ELSE '' END from radacct where AcctSessionId =
'57fc9e4821466d86';
ERROR: invalid input syntax for integer: ""
In the else case, this fallback return value comes into PostgreSQL as just
an empty string, which causes it to trip over - it sees that there's a
possibility to write an empty string into a bigint field, which provokes
the syntax error, even if the problem won't actually happen with this
particular setup of input data.
I'm not sure what to do... can the query be rewritten in a manner that would
allow for both use cases?
(Mailing list users, please Cc: responses for those of us who may not be
subscribed. TIA.)
--
2. That which causes joy or happiness.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Query using partitioned table hangs
Rob W writes: > A re-post, since I'm really stuck on this and could use some advice on how to > troubleshoot this... Have you looked into pg_locks to see if it's blocked waiting for a lock? The TRUNCATE in particular would require exclusive lock on the table, so it could be waiting for some other process that's touched the table. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Use a blob or not?
I want ot store chunks of data (only about five Kb each) on a database and have users download (across a network) these chunks to their local disk drive. Is a blob a good way to store these chunks? Thanks. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Use a blob or not?
On Mon, 2009-12-07 at 09:07 -0800, Daniel wrote: > I want ot store chunks of data (only about five Kb each) on a database > and have users download (across a network) these chunks to their local > disk drive. Is a blob a good way to store these chunks? Well we don't have "blob". We have bytea and lo (which is bytea with a different delivery and storage mechanism). 5k chunks is pretty small, bytea is probably fine. Joshua D. Drake > > Thanks. > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering If the world pushes look it in the eye and GRR. Then push back harder. - Salamander -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Use a blob or not?
Daniel, If the data will only be 5 Kb, I suggest you use bytea (binary string). Regards, Peter Geoghegan -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Add pg server to cluster
On Mon, Dec 7, 2009 at 10:35 AM, AlannY wrote: > Hi there. > > I'm using PostgreSQL as my main database engine. Everything works. > > I have one server for PostgreSQL, and space on it are lowing down. > > I want to buy a new server and somehow connect it with first one, that > PostgreSQL will use this new server's HDD. I don't want to buy new HDD > for the first server, because I don't have a space in server box. > > So, currently PostgreSQL data are located in /var/lib/pgsql/data > folder. If I connect new server, how should I connect new server's > folders to this directory, so PostgreSQL can add space for its data? > > Or maybe it's unreal to do? Unreal to use several network folders for > data? I'm new in clustering... Maybe it's possible to split up data > folder (and the mount it via NFS, for example)? > > You have a couple of options: NFS Works well, just make sure you're running with 'sync' enabled, or you could lose some data iSCSI Works slightly better, usually a more performant solution (in my experience). It's nice too because you could always upgrade to a hardware based iSCSI controller if need be. If you're looking to upgrade though, why not just move the database to the new server so that you can avoid this problem in the first place? Keeping the database running with local storage is usually going to perform better, unless you move up to an Enterprise SAN or something along those lines. --Scott
[GENERAL]
AlannY wrote: Hi there. I'm using PostgreSQL as my main database engine. Everything works. I have one server for PostgreSQL, and space on it are lowing down. I want to buy a new server and somehow connect it with first one, that PostgreSQL will use this new server's HDD. I don't want to buy new HDD for the first server, because I don't have a space in server box. For the requirements you've given above, buy an external storage array instead of a new server put a SAS card in your server, and a SAS/SATA bay as large as you need for additional disks.once these additional disks are formatted and mounted as a file system, which I'm going to call /u00 here, I'd do something like... 1) shut down postgres 2) mv /var/lib/pgsql/data /u00/pgdata 3) ln -s /u00/pgdata /var/lib/pgsql 4) restart postgres and poof, LOTS of space. example such enclosure, this one holds 12 3.5" SAS/SATA drives in a 2U chassis, and is strictly something I googled, I have no experience with the vendor or OEM http://www.aicipc.com/ProductDetail.aspx?ref=XJ1100%20series%20-%202U%2012-bay I would format a unit like this as raid10 using your OS's native raid (mdadm on linux, zpool on solaris, etc). for the SAS card, I'd lean towards a LSI Logic, such as http://www.lsi.com/storage_home/products_home/host_bus_adapters/sas_hbas/external/sas9200-8e/index.html -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Add pg server to cluster
On Mon, Dec 07, 2009 at 01:12:03PM -0500, Scott Mead wrote: > On Mon, Dec 7, 2009 at 10:35 AM, AlannY wrote: > > You have a couple of options: > > NFS > > Works well, just make sure you're running with 'sync' enabled, or > you could lose some data > What should I do exactly? Create NFS folder in new server? And then? Mount NFS folder to /var/lib/pgsql/data? If so, I will confront with space problem again, when space will ends at the new server... Or maybe there are more advanced modes with NFS? -- )\._.,--,'``. /, _.. \ _\ (`._ ,. `._.-(,_..'--(,_..'`-.;.' -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Add pg server to cluster
On Monday 07 December 2009, AlannY wrote: > What should I do exactly? Create NFS folder in new server? And then? > Mount NFS folder to /var/lib/pgsql/data? If so, I will confront with > space problem again, when space will ends at the new server... > > Or maybe there are more advanced modes with NFS? You can create tablespaces on different mount points. But seriously, don't use NFS across multiple servers for a database. Like another poster suggested, buy an external storage chassis and hook it up. -- "No animals were harmed in the recording of this episode. We tried but that damn monkey was just too fast." -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] how to ensure a client waits for a previous transaction to finish?
Hi, this is a bit of a noob question. I am using PGSql to perform some large analyses, with the clients being a sequentially run set of perl scripts (one to set up and populate tables and then down stream scripts to query the database for the results). During manual testing everything works, but automating it results in the query scripts starting before the population transactions having completed, so they give erroneous result. How can I ensure the query scripts wait until the population transaction processes have finished? I've looked at 'SET TRANSACTION ISOLATION LEVEL SERIALIZABLE' (to us in the query scripts I thought), but I'm not sure that is what I want. Can any one suggest where I should be looking, or if SET TRANSACTION is the right way to go? thanks -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Dan Kortschak writes: > How can I ensure the query scripts wait until the population transaction > processes have finished? I've looked at 'SET TRANSACTION ISOLATION LEVEL > SERIALIZABLE' (to us in the query scripts I thought), but I'm not sure > that is what I want. It's not. What you want is to COMMIT and make sure you've gotten the command completion response for that. Possibly perl is complicating matters with some sort of autocommit logic behind your back. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Dan Kortschak wrote: Hi, this is a bit of a noob question. I am using PGSql to perform some large analyses, with the clients being a sequentially run set of perl scripts (one to set up and populate tables and then down stream scripts to query the database for the results). when you say 'a series of perl scripts', do you mean separate perl files, each run as their own process? how are you invoking them? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Yes, they are separate perl files (I'm thinking that perhaps this wasn't the best way to do it now, but for the moment I'm going to have to stick with it). In the case of the manual testing it's jus a matter of command line calls. The automated runs call each script as part of a PBS torque script (essentially a sh script calls each in turn). cheers On Mon, 2009-12-07 at 13:16 -0800, John R Pierce wrote: > when you say 'a series of perl scripts', do you mean separate perl > files, each run as their own process? how are you invoking them? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Thanks for that, that should help me sort it out. I haven't used the autocommit option in pgdbi. I'll have a look to see if DBI::do has an option to wait for command completion. cheers On Mon, 2009-12-07 at 16:12 -0500, Tom Lane wrote: > It's not. What you want is to COMMIT and make sure you've gotten the > command completion response for that. Possibly perl is complicating > matters with some sort of autocommit logic behind your back. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
On Mon, Dec 7, 2009 at 4:00 PM, Dan Kortschak wrote: > During manual testing everything works, but automating it results in the > query scripts starting before the population transactions having > completed, so they give erroneous result. > Update your process to have the query scripts wait until the population scripts are done. Either that or have the populate script LOCK TABLE the first table that the query is going to use, and it will automatically block until your transaction is complete for populating. But really, it sounds like you have a process coordination problem, not a database problem. Hmmm you could use the DB to synchronize by having the query program LISTEN for an event and wait until that arrives, then have the populating program NOTIFY that event once it is done. Just select() on the Pg socket on the query program and once it is ready to read, check for any NOTIFY events that may have come. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Dan Kortschak wrote: Yes, they are separate perl files (I'm thinking that perhaps this wasn't the best way to do it now, but for the moment I'm going to have to stick with it). In the case of the manual testing it's jus a matter of command line calls. The automated runs call each script as part of a PBS torque script (essentially a sh script calls each in turn). I'm totally unfamiliar with torque., but you probably need to tell torque to run the first script and wait for it to return before running the rest, its probably launching a bunch concurrently. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
On Mon, Dec 7, 2009 at 4:21 PM, Dan Kortschak wrote: > The automated runs call each script as part of a PBS torque > script (essentially a sh script calls each in turn). > Sounds more like it calls them in parallel, else your populate script would have finished before your query script ran assuming they run in the right order. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] freeradius postgresql sql query glitch
- "Josip Rodin" wrote:
> Hi,
>
> I've observed an SQL logging problem with FreeRADIUS (2.x) and
> PostgreSQL
> (8.1), on several different installations I occasionally get these
> errors:
>
> Mon Dec 7 13:19:01 2009 : Error: [ourlittle_sql] Couldn't update SQL
> accounting STOP record - ERROR: invalid input syntax for integer: ""
>
>
> sql trace log indicates that this is the offending query:
>
> UPDATE radacct
>SET AcctStopTime = ('2009-12-07 13:19:01'::timestamp -
> '6'::interval),
>AcctSessionTime = CASE WHEN '' = '' THEN
>(EXTRACT(EPOCH FROM ('2009-12-07 13:19:01'::TIMESTAMP WITH TIME
> ZONE - AcctStartTime::TIMESTAMP WITH TIME ZONE
>- '6'::INTERVAL)))::BIGINT ELSE '' END,
>AcctInputOctets = (('0'::bigint << 32) + '0'::bigint),
>AcctOutputOctets = (('0'::bigint << 32) + '0'::bigint),
>AcctTerminateCause = 'User-Request',
>AcctStopDelay = 0,
>FramedIPAddress = NULLIF('4.3.2.1', '')::inet,
>ConnectInfo_stop = ''
>WHERE AcctSessionId = '57fc9e4821466d86'
>AND UserName = 'o...@user.name'
>AND NASIPAddress = '1.2.3.4'
>AND AcctStopTime IS NULL;
>
> I'm using the default unchanged sql/postgresql/dialup.conf setting:
>
> accounting_stop_query = "UPDATE ${acct_table2} \
> SET AcctStopTime = ('%S'::timestamp -
> '%{%{Acct-Delay-Time}:-0}'::interval), \
> AcctSessionTime = CASE WHEN '%{Acct-Session-Time}' = '' THEN \
>
> (EXTRACT(EPOCH FROM ('%S'::TIMESTAMP WITH TIME ZONE -
> AcctStartTime::TIMESTAMP WITH TIME ZONE \
> - '%{%{Acct-Delay-Time}:-0}'::INTERVAL)))::BIGINT ELSE
> '%{Acct-Session-Time}' END, \
> AcctInputOctets = (('%{%{Acct-Input-Gigawords}:-0}'::bigint << 32) +
> '%{%{Acct-Input-Octets}:-0}'::bigint), \
> AcctOutputOctets = (('%{%{Acct-Output-Gigawords}:-0}'::bigint << 32)
> + '%{%{Acct-Output-Octets}:-0}'::bigint), \
> AcctTerminateCause = '%{Acct-Terminate-Cause}', \
> AcctStopDelay = 0, \
> FramedIPAddress = NULLIF('%{Framed-IP-Address}', '')::inet, \
> ConnectInfo_stop = '%{Connect-Info}' \
> WHERE AcctSessionId = '%{Acct-Session-Id}' \
> AND UserName = '%{SQL-User-Name}' \
> AND NASIPAddress = '%{NAS-IP-Address}' \
> AND AcctStopTime IS NULL"
>
> Looks like the code wants to use CASE to check whether
> %{Acct-Session-Time}
> exists among the internal FreeRADIUS variables, while the return value
> of
> the whole SQL CASE construct is supposed to be a bigint.
>
> This is a reduced failing case:
>
> radiustmobile=# select CASE WHEN '' = '' THEN (EXTRACT(EPOCH FROM
> ('2009-12-07 13:19:01'::TIMESTAMP WITH TIME ZONE -
> AcctStartTime::TIMESTAMP WITH TIME ZONE - '6'::INTERVAL)))::BIGINT
> ELSE '' END from radacct where AcctSessionId = '57fc9e4821466d86';
> ERROR: invalid input syntax for integer: ""
>
> In the else case, this fallback return value comes into PostgreSQL as
> just
> an empty string, which causes it to trip over - it sees that there's
> a
> possibility to write an empty string into a bigint field, which
> provokes
> the syntax error, even if the problem won't actually happen with this
> particular setup of input data.
>
> I'm not sure what to do... can the query be rewritten in a manner that
> would
> allow for both use cases?
If I understand correctly the below may work. If %{Acct-Session-Time} is an
empty string it will return NULL otherwise it will return %{Acct-Session-Time}.
ELSE
NULLIF('%{Acct-Session-Time}','') END,
See here details:
http://www.postgresql.org/docs/8.1/interactive/functions-conditional.html#AEN12697
Adrian Klaver
akla...@comcast.net
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
Thanks to everyone who has answered this. The short answer is that torque is not behaving the way I expected and not the way I have ever seen it behave in the past. The I/O binding of these jobs may have something to do with this, but I will look into it further. cheers On Mon, 2009-12-07 at 13:26 -0800, John R Pierce wrote: > I'm totally unfamiliar with torque., but you probably need to tell > torque to run the first script and wait for it to return before > running > the rest, its probably launching a bunch concurrently. > That *shouldn't* be the case as the contents of a torque script should be run sequentially (many jobs depend on this and I've never seen job parts run out of order), just as a sh script is (they are actually just csh scripts in my case). My understanding is that the parallelisation occurs either through using MPI or other parallel compilers or running a number of torque jobs, BUT I've just tested the hypothesis by running it as a straight csh script - and it works perfectly, so there must be something like that going on. I'll ask some of our more experience torque admins about it. Thanks. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] how to ensure a client waits for a previous transaction to finish?
On Mon, Dec 7, 2009 at 5:32 PM, Dan Kortschak wrote: > Thanks to everyone who has answered this. The short answer is that > torque is not behaving the way I expected and not the way I have ever > seen it behave in the past. The I/O binding of these jobs may have > something to do with this, but I will look into it further. > > cheers > > On Mon, 2009-12-07 at 13:26 -0800, John R Pierce wrote: >> I'm totally unfamiliar with torque., but you probably need to tell >> torque to run the first script and wait for it to return before >> running >> the rest, its probably launching a bunch concurrently. >> > That *shouldn't* be the case as the contents of a torque script should > be run sequentially (many jobs depend on this and I've never seen job > parts run out of order), just as a sh script is (they are actually just > csh scripts in my case). My understanding is that the parallelisation > occurs either through using MPI or other parallel compilers or running a > number of torque jobs, BUT I've just tested the hypothesis by running it > as a straight csh script - and it works perfectly, so there must be > something like that going on. I'll ask some of our more experience > torque admins about it. Thanks. If it turns out you need to have a lock with a 'longer than transaction' duration, maybe advisory locks are a good fit. merlin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Tuesday (PST8PDT) Jeff Davis Presents: Operator Exclusion Constraints
Folks, If you can't make it to the SFPUG meeting in person on Tuesday, December 8, 2009 at EZRez http://postgresql.meetup.com/1/calendar/11928447/ You can see the live stream at: http://media.postgresql.org/sfpug/streaming/ We'll also be using an irc channel for questions, comments, etc: irc://irc.freenode.net/sfpug Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] freeradius postgresql sql query glitch
On Mon, Dec 07, 2009 at 10:02:39PM +, Adrian Klaver wrote:
> > Mon Dec 7 13:19:01 2009 : Error: [ourlittle_sql] Couldn't update SQL
> > accounting STOP record - ERROR: invalid input syntax for integer: ""
> >
> > accounting_stop_query = "UPDATE ${acct_table2} \
> > SET
> > AcctSessionTime = CASE WHEN '%{Acct-Session-Time}' = '' THEN \
> > (EXTRACT(EPOCH FROM ('%S'::TIMESTAMP WITH TIME ZONE -
> > AcctStartTime::TIMESTAMP WITH TIME ZONE \
> > - '%{%{Acct-Delay-Time}:-0}'::INTERVAL)))::BIGINT ELSE
> > '%{Acct-Session-Time}' END, \
> >
> > I'm not sure what to do... can the query be rewritten in a manner that
> > would
> > allow for both use cases?
>
> If I understand correctly the below may work. If %{Acct-Session-Time} is
> an empty string it will return NULL otherwise it will return
> %{Acct-Session-Time}.
>
> ELSE
> NULLIF('%{Acct-Session-Time}','') END,
Thanks, that should work, with a slight modification - explicit cast to
'bigint', because a nullif()'ed '' is still a 'text' by default.
The two cases then evaluate like this:
pgsql=# select CASE WHEN '' = '' THEN 1234::BIGINT ELSE NULLIF('', '')::BIGINT
END AS value;
value
---
1234
(1 row)
pgsql=# select CASE WHEN '13' = '' THEN 1234::BIGINT ELSE NULLIF('13',
'')::BIGINT END AS value;
value
---
13
(1 row)
--
2. That which causes joy or happiness.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [HACKERS] New PostgreSQL Committers
2009/12/8 Kevin Grittner : > Jaime Casanova wrote: >> Dave Page wrote: >>> >>> The new committers are: >>> >>> Robert Haas >>> Simon Riggs >>> Greg Stark >>> ITAGAKI Takahiro >>> >>> Congratulations! >>> >> >> +1 > > Outstanding! Congratulations, all! +1 Appreciate for their contributions. Congratulations all! Koichi Suzuki > > -Kevin > > -- > Sent via pgsql-hackers mailing list (pgsql-hack...@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Use a blob or not?
On December 7, 2009 12:07:49 pm Daniel wrote: > I want ot store chunks of data (only about five Kb each) on a database > and have users download (across a network) these chunks to their local > disk drive. Is a blob a good way to store these chunks? > > Thanks. > Put me on the list of recommending bytea, It works well for me, I use it for my virus database, and have noticed no perceptable lag from ~100k samples averaging probably 100kb. Colin -- Best of all is never to have been born. Second best is to die soon. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Error to install Slony I on Postgresql
Dear All, I have a server :SUSE Linux Enterprise Server 10 (x86_64) postgresql-8.31.i586 is installed on this server. When I install slony1-2.0.2, I have a error "Your version of libpq doesn't have PQunescapeBytea which means that your version of PostgreSQL is lower than 7.3 and thus not even remotely supported by Slony-I version 2 " I can fix this error on SUSE Linux Enterprise Server 10 (i586). But when i apply the same way to fix it on SUSE Linux Enterprise Server 10 (x86_64), i'm not successful Can you help me ?? Please !!! -- View this message in context: http://old.nabble.com/Error-to-install-Slony-I-on-Postgresql-tp26687956p26687956.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error to install Slony I on Postgresql
On Mon, Dec 7, 2009 at 7:56 PM, maiphan2008 wrote: > > Dear All, > > I have a server :SUSE Linux Enterprise Server 10 (x86_64) > postgresql-8.31.i586 is installed on this server. > > When I install slony1-2.0.2, I have a error "Your version of libpq doesn't > have PQunescapeBytea which means that your version of PostgreSQL is > lower than 7.3 and thus not even remotely supported by Slony-I version > 2 " 1: Slony 1 V2 isn't really ready for prime time yet. I installed it a few months ago in production on 8.3.8 and it promptly started causing phantom locks to appear that hung the whole db and replication engine requiring db restarts. We had more downtime in a week than we'd had in the previous year. 2: Are you sure you're using the latest libpq in that instance and that you don't have an old one installed somehow somewhere? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Help! xlog flush request is not satisfied
On 7/12/2009 3:00 PM, A B wrote: Hi. I just logged into a system and found this in the log when trying to start postgres. Possibly silly question: is there plenty of free disk space on the file system where PostgreSQL's data is stored? -- Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Help! xlog flush request is not satisfied
Craig Ringer writes: > On 7/12/2009 3:00 PM, A B wrote: >> I just logged into a system and found this in the log when trying to >> start postgres. > Possibly silly question: is there plenty of free disk space on the file > system where PostgreSQL's data is stored? That's not what that message is about. What it's unhappy about is that it found a page with an LSN that's past the logical end of WAL. This either means that page is corrupt, or there's something wrong with WAL. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error to install Slony I on Postgresql
Scott Marlowe-2 wrote: > > On Mon, Dec 7, 2009 at 7:56 PM, maiphan2008 wrote: >> >> Dear All, >> >> I have a server :SUSE Linux Enterprise Server 10 (x86_64) >> postgresql-8.31.i586 is installed on this server. >> >> When I install slony1-2.0.2, I have a error "Your version of libpq >> doesn't >> have PQunescapeBytea which means that your version of PostgreSQL is >> lower than 7.3 and thus not even remotely supported by Slony-I >> version >> 2 " > > 1: Slony 1 V2 isn't really ready for prime time yet. I installed it a > few months ago in production on 8.3.8 and it promptly started causing > phantom locks to appear that hung the whole db and replication engine > requiring db restarts. We had more downtime in a week than we'd had > in the previous year. > > 2: Are you sure you're using the latest libpq in that instance and > that you don't have an old one installed somehow somewhere? > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > > Thanks Scott Marlowe-2. 1. I will consider more. 2. I read config.log file. And I see: /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /usr/lib/libpq.so when searching for -lpq /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /usr/lib/libpq.a when searching for -lpq /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: cannot find -lpq It is conflicted between 32bit and 64 bit. Do you know to compile them?? Thank you. -- View this message in context: http://old.nabble.com/Error-to-install-Slony-I-on-Postgresql-tp26687956p26688657.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error to install Slony I on Postgresql
On Mon, Dec 7, 2009 at 9:42 PM, maiphan2008 wrote: > > > > Scott Marlowe-2 wrote: >> >> On Mon, Dec 7, 2009 at 7:56 PM, maiphan2008 wrote: >>> >>> Dear All, >>> >>> I have a server :SUSE Linux Enterprise Server 10 (x86_64) >>> postgresql-8.31.i586 is installed on this server. >>> >>> When I install slony1-2.0.2, I have a error "Your version of libpq >>> doesn't >>> have PQunescapeBytea which means that your version of PostgreSQL is >>> lower than 7.3 and thus not even remotely supported by Slony-I >>> version >>> 2 " >> >> 1: Slony 1 V2 isn't really ready for prime time yet. I installed it a >> few months ago in production on 8.3.8 and it promptly started causing >> phantom locks to appear that hung the whole db and replication engine >> requiring db restarts. We had more downtime in a week than we'd had >> in the previous year. >> >> 2: Are you sure you're using the latest libpq in that instance and >> that you don't have an old one installed somehow somewhere? >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general >> >> > > Thanks Scott Marlowe-2. > 1. I will consider more. > 2. I read config.log file. And I see: > /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: > skipping incompatible /usr/lib/libpq.so when searching for -lpq > /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: > skipping incompatible /usr/lib/libpq.a when searching for -lpq > /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: > cannot find -lpq > > It is conflicted between 32bit and 64 bit. Do you know to compile them?? You might need some libpq devel packages to be installed... Other than that I'm lost. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Error to install Slony I on Postgresql
P.s. I build slony I v 1.2.x all the time on 64 bit Centos with no problems at all. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
