Sorry if it is already known but just to be sure the 8.2.14 source
rpms are missing from the yum repository.
Regards, Clodoaldo
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
2009/9/12 Devrim GÜNDÜZ dev...@gunduz.org:
On Sat, 2009-09-12 at 12:22 -0300, Clodoaldo Neto wrote:
Sorry if it is already known but just to be sure the 8.2.14 source
rpms are missing from the yum repository.
Because of bandwith issues on the master RPM build server, srpms are
uploaded
I can't install the 8.2.14 or 8.4.1 source rpms:
# rpm -Uhv postgresql-8.2.14-1PGDG.f11.src.rpm
warning: postgresql-8.2.14-1PGDG.f11.src.rpm: Header V4 DSA signature:
NOKEY, key ID 442df0f8
1:postgresql warning: user devrim does not exist - using root
warning: group devrim does not
2009/9/18 Devrim GÜNDÜZ dev...@gunduz.org:
Hi Clodoaldo,
On Fri, 2009-09-18 at 19:42 -0300, Clodoaldo Neto wrote:
# rpm -Uhv postgresql-8.2.14-1PGDG.f11.src.rpm
warning: postgresql-8.2.14-1PGDG.f11.src.rpm: Header V4 DSA signature:
NOKEY, key ID 442df0f8
1:postgresql warning
postgresql.x86_64 8.3.14-1PGDG.rhel5
postgresql-server.x86_64 8.3.14-1PGDG.rhel5
ERROR: operator does not exist: integer = integer
LINE 3:inner join vendedor as v on a.vendedor_id = v.id
2011/8/1 Clodoaldo Neto clodoaldo.pinto.n...@gmail.com
postgresql.x86_64 8.3.14-1PGDG.rhel5
postgresql-server.x86_64 8.3.14-1PGDG.rhel5
ERROR: operator does not exist: integer = integer
LINE 3:inner join vendedor as v
I have a very frequently updated table with 240 million rows (and growing).
Every three hours 1.5 million rows are inserted and 1.5 million are
deleted. When I moved the cluster to a SSD this bulk insert (using copy)
time was cut from 22 minutes to 2.3 minutes. The deletion time was also
improved.
Em 26 de fevereiro de 2012 12:45, Clodoaldo Neto
clodoaldo.pinto.n...@gmail.com escreveu:
When I explain a query using a partitioned table the result is the
expected. That is, only the corrected partition is scanned. But when the
query is inside a plpgsql function it takes forever to complete
I have both 9.0 and 9.1 installed in Centos 6:
postgresql90.x86_64 9.0.7-1PGDG.rhel6
@pgdg90
postgresql90-docs.x86_64 9.0.7-1PGDG.rhel6
@pgdg90
postgresql90-libs.x86_64 9.0.7-1PGDG.rhel6
@pgdg90
postgresql90-odbc.x86_64
template1=# create extension plpythonu;
ERROR: could not open extension control file
/usr/pgsql-9.1/share/extension/plpythonu.control: No such file or
directory
The package is installed:
postgresql91-plpython.x86_64 9.1.3-1PGDG.rhel6@pgdg91
# ll /usr/pgsql-9.1/share/extension/
total 12
Em 28 de fevereiro de 2012 17:48, Devrim GÜNDÜZ dev...@gunduz.orgescreveu:
Hi,
On Tue, 2012-02-28 at 17:39 -0300, Clodoaldo Neto wrote:
template1=# create extension plpythonu;
ERROR: could not open extension control file
/usr/pgsql-9.1/share/extension/plpythonu.control: No such file
Em 28 de fevereiro de 2012 17:54, Devrim GÜNDÜZ dev...@gunduz.orgescreveu:
Hi,
On Tue, 2012-02-28 at 10:33 -0300, Clodoaldo Neto wrote:
snip
Transaction Check Error:
file /usr/lib64/python2.6/site-packages/_pg.so from install of
postgresql91-python-0:4.0-2PGDG.rhel6.x86_64
In 9.1.3 the client encoding is not defaulting to the db encoding:
postgresql.conf:
#client_encoding = sql_ascii
= show server_encoding;
server_encoding
-
SQL_ASCII
= show client_encoding;
client_encoding
-
UTF8
In 9.0 the client encoding defaults to the db
I have gone through the issue of making a parent table not writable. After
discussing it (1) I adopted the trigger solution. But I think that a
trigger is just an invisible layer over the database model and so I'm
naively proposing a new syntax to postgresql. It would inform that the
check
Em 12 de abril de 2012 14:12, Phoenix Kiula phoenix.ki...@gmail.comescreveu:
I had pgbouncer working somehow, but we have switched servers recently
and now I cannot for the life of me figure out again how to set it up.
Online guides say things like create a user ID. Well, where? Inside
PG
Em 14 de abril de 2012 09:39, raghu ram raghuchenn...@gmail.com escreveu:
On Sat, Apr 14, 2012 at 4:31 PM, Clodoaldo Neto
clodoaldo.pinto.n...@gmail.com wrote:
Em 12 de abril de 2012 14:12, Phoenix Kiula
phoenix.ki...@gmail.comescreveu:
I had pgbouncer working somehow, but we have
2012/3/5 Clodoaldo Neto clodoaldo.pinto.n...@gmail.com
I have gone through the issue of making a parent table not writable. After
discussing it (1) I adopted the trigger solution. But I think that a
trigger is just an invisible layer over the database model and so I'm
naively proposing a new
I have postgresql91-contrib installed in Centos 6:
# yum list installed postgresql91-contrib
...
Installed Packages
postgresql91-contrib.x86_64 9.1.4-1PGDG.rhel6 @pgdg91
But when I try to use it I get the error:
ERROR: function dblink(text, text) does not exist
LINE 2: from dblink(
2012/6/11 Vibhor Kumar vibhor.ku...@enterprisedb.com
On Jun 11, 2012, at 11:17 AM, Clodoaldo Neto wrote:
I have postgresql91-contrib installed in Centos 6:
# yum list installed postgresql91-contrib
...
Installed Packages
postgresql91-contrib.x86_64 9.1.4-1PGDG.rhel6 @pgdg91
How does the planner know that the function used in an index has changed?
If the function's body is changed keeping the argument and return types the
planner will not use it anymore:
create table t (i integer);
insert into t (i)
select generate_series(1, 10);
analyze t;
A simple function to
I'm trying to upgrade Postgresql from 9.2 to 9.3 in Fedora 18 using this
command as the postgres user
$ pg_upgrade -b /bin -B /usr/pgsql-9.3/bin -d /var/lib/pgsql/data -D
/var/lib/pgsql/9.3/data/ -j 2 -u postgres
The error in the log:
command: /bin/pg_ctl -w -l pg_upgrade_server.log -D
(cluster-major_version) 903) ?*
*, in my case i change it to:*
*199: (GET_MAJOR_VERSION(cluster-major_version) 900) **?*
Clodoaldo
2013/9/18 Clodoaldo Neto clodoaldo.pinto.n...@gmail.com
I'm trying to upgrade Postgresql from 9.2 to 9.3 in Fedora 18 using this
command as the postgres
I can connect to Heroku with psql passing a URI as generated by
http://api.postgression.com:
$ psql
postgres://hcnkrxukvhqiww:lryfxzcmlboytgtxpsvla8h...@ec2-107-21-93-97.compute-1.amazonaws.com:5432/dearu2qcqcmi7t
I want to do the same with pgAdmin:
$ pgadmin3 -qc
I don't know the policy of package inclusion in the repositories. The
plpython3 package exists in the Fedora repository:
http://mirror.globo.com/fedora/linux/updates/22/x86_64/p/
But it does not exist in the Postgresql repository:
Trying to upgrade 9.4 and 9.5 in Fedora 22:
# dnf upgrade
...
Error: Package postgresql94-9.4.7-1PGDG.f22.x86_64.rpm is not signed
Regards, Clodoaldo
Trying to install Pgadmin4 Web in Centos7:
# yum list installed pgadmin4\*
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: mirror.linuxfix.com
* epel: mirror.sjc02.svwh.net
* extras: centos.mirror.ndchost.com
* updates: centos.mirror.ndchost.com
34
It is fixed now. Thanks!
Clodoaldo
On Sun, Jul 16, 2017 at 8:39 AM, Devrim Gündüz <dev...@gunduz.org> wrote:
>
> Hi Clodoaldo,
>
> On Sat, 2017-07-15 at 08:38 -0300, Clodoaldo Neto wrote:
> > While installing Psycopg2 for Python2 in Fedora 26 having Postgresql 9.6:
>
While installing Psycopg2 for Python2 in Fedora 26 having Postgresql 9.6:
# dnf install python-psycopg2
Last metadata expiration check: 0:01:52 ago on Sat 15 Jul 2017 08:30:26 AM
-03.
Error:
Problem: conflicting requests
- nothing provides postgresql94-libs needed by
On Mon, Apr 24, 2017 at 11:15 AM, Adrian Klaver <adrian.kla...@aklaver.com>
wrote:
> On 04/24/2017 05:06 AM, Clodoaldo Neto wrote:
> Please reply to list also
> Ccing list
>
> On Sun, Apr 23, 2017 at 4:58 PM, Adrian Klaver
>> <adrian.kla...@aklaver.com <mailto:
When upgrading from https://download.postgresql.org/pub/repos/yum/10/fedora/
# dnf upgrade
...
Error: Package postgresql10-10.1-1PGDG.f25.x86_64.rpm is not signed
Regards, Clodoaldo
30 matches
Mail list logo
