How can I run a PostgreSQL database independently of the normal packaged
based configuration?
I just want to start up postgres or pg_ctl process using a different port,
pointing to a different data directory and get it running, with permissions
etc working okay.
I don't want it to depend on the
Hi,
For some operations, such as INSERT/UPDATE, heap relation lock is held until
xact commit, but index relation lock is released after command end. Some other
operations also hold index relation lock until xact commit, such as VACUUM.
I have read chapter 54. Index Access Method Interface Def
I found this via dzone.com. Its self-described as being intermediate level
topic coverage, and I agree, but even beginners should get some valuable
insights from it.
http://tech.pro/tutorial/1631/5-claims-about-sql-explained
It is well written and product agnostic though much of what is discusse
I've got a bunch of independent database clusters, each with a couple of
streaming replication slaves. I'm starting to upgrade them to 9.1.10, but on 3
of the 3 I've tried so far, this has somehow resulted in data corruption. I'm
hoping it was the upgrade itself that caused the corruption, inste
Hi,
I am trying to build my database with a metric index. I am using a Fixed Query
Array.
I have got a table with many sentences of natural languages. I'm using the Dice
Coefficient for calculating the metric space.
I am going to take a certain number of sentences and use them as pivots by
calc
Gregory Haase writes:
> The json_data column is not accounted for in pg_stats:
Ah! I hadn't twigged to the fact that your bloat measurement approach
assumed you had pg_stats entries for all the columns.
> So I'm not sure if I'd actually qualify this as a "bug", but it appears
> that there is no
I spent some more time on this today, and I realized that the issue isn't
that there are records in the toast table. The issue is that there are NO
records in the toast table. Apparently, all the json we are inserting are
too small to get toasted.
I setup a separate benchmark locally:
create table
Laurent Sartran wrote:
> CREATE MATERIALIZED VIEW t1 AS SELECT text 'foo' AS col1
> WITH NO DATA;
> CREATE MATERIALIZED VIEW t2b AS SELECT * FROM t1
> WHERE col1 = (SELECT LEAST(col1) FROM t1)
> WITH NO DATA;
>
> ERROR: materialized view "t1" has not been populated
> HINT: Use the REFRESH
Again, this output indicates that pgbouncer is not connecting to postgres
server.
Regards,
Igor Neyman
On Thu, Oct 31, 2013 at 11:02 AM, si24 wrote:
> I don't know if this will help in terms of my problem?
>
> this came from the admin pgbouncer console.
>
>
>
> pgbouncer=# show servers;
> typ
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Birta Levente
> Sent: Friday, November 01, 2013 9:50 AM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Re: changing port numbers so pgbouncer can read
> g
On 11/01/2013 06:29 AM, Birta Levente wrote:
geoserver is using port 8080, some how they don't seem to be speaking to
each other.
I don't know what is this geoserver, but this port 8080 I think it's not
relevant in this.
If I am following correctly the OP chain of connections as origina
On 01/11/2013 15:39, si24 wrote:
have you specified in your pgbouncer.ini auth_type and auth_file ?
my auth_type is md5 and my auth_file is D:\Program
Files\PostgreSQL\etc\userlist.txt
And I think you really need to check pgbouncer log !!!
I get a lot of this im my pgbouncer log
2013-11-01
On 01/11/2013 15:39, si24 wrote:
have you specified in your pgbouncer.ini auth_type and auth_file ?
my auth_type is md5 and my auth_file is D:\Program
Files\PostgreSQL\etc\userlist.txt
And I think you really need to check pgbouncer log !!!
I get a lot of this im my pgbouncer log
2013-11-01
>have you specified in your pgbouncer.ini auth_type and auth_file ?
my auth_type is md5 and my auth_file is D:\Program
Files\PostgreSQL\etc\userlist.txt
>And I think you really need to check pgbouncer log !!!
I get a lot of this im my pgbouncer log
2013-11-01 12:17:49.228 2860 LOG Stats: 0 r
On 01/11/2013 14:44, si24 wrote:
I get this error in geoserver :Original exception error:
Unable to obtain connection: Cannot create PoolableConnectionFactory (ERROR:
client_login_timeout (server down))
when I change the store port number from 5432 to 6432 so that geoserver can
use the pgbounc
I get this error in geoserver :Original exception error:
Unable to obtain connection: Cannot create PoolableConnectionFactory (ERROR:
client_login_timeout (server down))
when I change the store port number from 5432 to 6432 so that geoserver can
use the pgbouncer instead of calling on the postg
On 01/11/2013 09:46, si24 wrote:
So should I rather change the 6432 to 5432 like the postgresql port or 8080
like the geoserver tomcat port.
Yes, you could do like this... but have to change psql server's port too
... to other than 5432... and tell pgbouncer to which port connect to
postgresq
So should I rather change the 6432 to 5432 like the postgresql port or 8080
like the geoserver tomcat port.
Geoserver is on 8080 and reads all the tables that postgres has cause you
need to add the port no that postgres is on to be able for it read the
tables.
--
View this message in context:
On 01/11/2013 09:07, si24 wrote:
geoserver uses the same port number as tomcat does which 8080 as the moment
should I change it to something else?
postgres uses 5432(default port number to postgresql) and pgbouncer uses
6432(default port number given to pgbouncer)
Am I missed something or you
Sergey Konoplev wrote:
>> As far as I know, the application programs do not make any
>> specific lock on the 'file' table. I'm not sure if it is caused
>> by the pgpool or something else.
>
> [...]
>
>> 2013-10-31 18:01:30 UTCLOG: sending cancel to blocking autovacuum PID 8614
>> 2013-10-31 18:
geoserver uses the same port number as tomcat does which 8080 as the moment
should I change it to something else?
postgres uses 5432(default port number to postgresql) and pgbouncer uses
6432(default port number given to pgbouncer)
--
View this message in context:
http://postgresql.1045698.n5.
21 matches
Mail list logo
