On Thu, Jan 23, 2014 at 3:46 PM, Bill Moran wrote:
> It was suggested that
> leaving the constraints as NOT VALID might affect the planner, causing
> it to use less optimal plans because it doesn't think it can trust
> the constraint. Is this true?
AFAICT the planner doesn't currently rely on FO
Hello,
I'm currently testing postgres_fdw feature on PostgreSQL 9.3.2 and I have some
questions:
- What are the limits to the number of foreign tables ?
- What is the current status about foreign joins push-down ?
Thanks in advance,
--
<>
--
Sent via pgsql-general mailing list (pgsql-gener
Hi,
I have a Postgresql-7.4.19 database in SQL_ASCII Encoding format. There is
a table, besides other tables, in the database, that is used to store BLOBs
through a Web-based application. I normally take database backup using
pg_dump, as and when needed, and it has always worked fine. It wa
2014/1/24 Emmanuel Medernach :
> Hello,
>
> I'm currently testing postgres_fdw feature on PostgreSQL 9.3.2 and I have
> some questions:
>
> - What are the limits to the number of foreign tables ?
As far as I know, there is no limit (beyond the usual PostgreSQL limits).
> - What is the current s
On 24 January 2014 09:20, Emmanuel Medernach wrote:
> Hello,
>
> I'm currently testing postgres_fdw feature on PostgreSQL 9.3.2 and I have
> some questions:
>
> - What are the limits to the number of foreign tables ?
As far as I'm aware, there isn't one.
> - What is the current status about fo
On Fri, Jan 24, 2014 at 4:20 AM, Emmanuel Medernach <
meder...@clermont.in2p3.fr> wrote:
> Hello,
>
> I'm currently testing postgres_fdw feature on PostgreSQL 9.3.2 and I have
> some questions:
>
> - What are the limits to the number of foreign tables ?
> - What is the current status about forei
$dbh = DBI->connect("dbi:Pg:dbname=$dbname;host=${dbserver};port=$dbport;",
$dbuser, $dbpasswd) or
errexit( "Unable to connect to dbname $dbname, err: $DBI::errstr");
The exact same connection string works fine in a standalone perl program.
Susan
On Thu, Jan 23, 2014 at 3:08 PM, Adrian Klaver
Susan Cassidy writes:
> $dbh = DBI->connect("dbi:Pg:dbname=$dbname;host=${dbserver};port=$dbport;",
> $dbuser, $dbpasswd) or
> errexit( "Unable to connect to dbname $dbname, err: $DBI::errstr");
> The exact same connection string works fine in a standalone perl program.
Given the permissions er
On 01/24/2014 09:35 AM, Susan Cassidy wrote:
I've already checked that. It is enabled. I am running Scientific Linux.
SELinux is enabled?
The database connection value is enabled to allow or disallow webserver
connections?
On Fri, Jan 24, 2014 at 8:28 AM, Tom Lane mailto:t...@sss.pgh.pa
I've already checked that. It is enabled. I am running Scientific Linux.
On Fri, Jan 24, 2014 at 8:28 AM, Tom Lane wrote:
> Susan Cassidy writes:
> > $dbh =
> DBI->connect("dbi:Pg:dbname=$dbname;host=${dbserver};port=$dbport;",
> > $dbuser, $dbpasswd) or
> > errexit( "Unable to connect to d
Are you calling the perl from apache (assuming yes)..? Does the web
user have the rights to execute the perl code?
Try disabling SELinux..
You'll get it..
On Fri, 2014-01-24 at 09:35 -0800, Susan Cassidy wrote:
> I've already checked that. It is enabled. I am running Scientific
> Linux.
>
>
>
[scassidy@jacensolo ~]$ /usr/sbin/sestatus | grep SELinux
SELinux status: enabled
SELinuxfs mount:/selinux
I have yet to find what to do to enable webserver connections.
Susan
On Fri, Jan 24, 2014 at 9:38 AM, Adrian Klaver wrote:
> On 01/24/2014 09:35 AM, Susan
I don't actually know what SELinux is. What else will happen if I (find
out how to) disable it?
Susan
On Fri, Jan 24, 2014 at 9:47 AM, Bret Stern <
bret_st...@machinemanagement.com> wrote:
> Are you calling the perl from apache (assuming yes)..? Does the web
> user have the rights to execute t
Susan Cassidy wrote:
> [scassidy@jacensolo ~]$ /usr/sbin/sestatus | grep SELinux
> SELinux status: enabled
> SELinuxfs mount:/selinux
>
> I have yet to find what to do to enable webserver connections.
setsebool -P httpd_can_network_connect_db 1
Best rega
I tried:
setsebool -P httpd_can_network_connect 1
But I get:
Cannot set persistent booleans without managed policy.
Could not change policy booleans
I don't know what that means.
Susan
On Fri, Jan 24, 2014 at 9:38 AM, Adrian Klaver wrote:
> On 01/24/2014 09:35 AM, Susan Cassidy wrote:
>
>>
Susan Cassidy wrote:
> Cannot set persistent booleans without managed policy.
> Could not change policy booleans
>
> I don't know what that means.
It probably means you're not root when issuing that command.
Become root or use sudo.
Best regards,
--
Daniel
PostgreSQL-powered mail user
On 1/24/2014 11:55 AM, Susan Cassidy wrote:
I don't actually know what SELinux is. What else will happen if I
(find out how to) disable it?
your system will be less secure.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent vi
Manoj Agarwal wrote:
> I have a Postgresql-7.4.19 database
Did you mean 8.4.19 or are you really running on a release which
has been out of support since 2010?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-general mailing list (pgsql-g
SELINUX is a bunch of settings to control security.
If you are able to find it, I was suggesting you disable it
only to see if the Apache problem goes away.
Then to turn it back on.
If it stops working, then there is a setting which is preventing
Apache from being accessed. Locating the specific
On 1/24/2014 12:19 PM, Bret Stern wrote:
SELINUX is a bunch of settings to control security.
If you are able to find it, I was suggesting you disable it
only to see if the Apache problem goes away.
do NOT disable it. set the selinux policy to 'permissive'.this
causes it to log exceptions
Hello to all,
I always use PostgreSQL from enterpriseDB. I have both 9.2 and 9.1 latest
verions installed on two different Ubuntu 64bit machines. For some reason
levenshtein_less_equal does not work, in contrast to levenshtein which works
as expected. I even downloaded the src code for PostgreSQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2014 12:50 PM, alexandros_e wrote:
> For some reason levenshtein_less_equal does not work,
Define "does not work", i.e. cut and paste exact SQL and output so we
can see and reproduce your issue.
Joe
- --
Joe Conway
credativ LLC: http://www
Query:
SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
ERROR: function levenshtein_less_equal(unknown, unknown, integer) does not
exist
LINE 1: SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
^
HINT: No function matches the given name and argument types. Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2014 01:07 PM, alexandros_e wrote:
> SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
Did you CREATE the extension?
8<-
psql (9.3.2)
Type "help" for help.
iftest=# SELECT levenshtein_less_equal('exte
On 01/24/2014 01:07 PM, alexandros_e wrote:
Query:
SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
ERROR: function levenshtein_less_equal(unknown, unknown, integer) does not
exist
LINE 1: SELECT levenshtein_less_equal('extensive', 'exhaustive',2);
^
HINT: No functi
Just this:
create extension fuzzystrmatch;
If the extension was not installed, then the simple levenstein distance
would not work either.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/levenshtein-less-equal-does-not-work-tp5788710p5788715.html
Sent from the Postgre
On 01/24/2014 01:19 PM, alexandros_e wrote:
Just this:
create extension fuzzystrmatch;
If the extension was not installed, then the simple levenstein distance
would not work either.
Which is what makes me think you are not connecting to the server you
think you are.
--
View this messag
SELECT version();
and
\df levenshtein_less_equal
"PostgreSQL 9.1.11 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
20080704 (Red Hat 4.1.2-52), 64-bit"
routing_nw2=# \df levenshtein_less_equal
List of functions
Schema | Name | Result data type | Argument
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2014 01:28 PM, alexandros_e wrote:
> SELECT version();
>
> and
>
> \df levenshtein_less_equal
>
> "PostgreSQL 9.1.11 on x86_64-unknown-linux-gnu, compiled by gcc
> (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52), 64-bit"
>
> routing_nw2=# \df le
=# \dx
List of installed extensions
Name | Version | Schema | Description
-+-++--
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
(1 row)
-# \df levenshtein*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2014 01:38 PM, alexandros_e wrote:
> =# \dx List of installed extensions Name | Version | Schema |
> Description
> -+-++--
> plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural l
On 01/24/2014 01:38 PM, alexandros_e wrote:
=# \dx
List of installed extensions
Name | Version | Schema | Description
-+-++--
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
(1 row)
-# \df
With your help I found the solution. My DB was initially based on a 9.0
server and I had restored it on the 9.1 server. For some reason 9.0
fuzzystrmatch functions (levenstein...) were already present in this DB. So,
CREATE EXTENSION fuzzystrmatch did not work. I had to manually remove
function 9.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2014 02:07 PM, alexandros_e wrote:
> With your help I found the solution. My DB was initially based on a
> 9.0 server and I had restored it on the 9.1 server. For some reason
> 9.0 fuzzystrmatch functions (levenstein...) were already present i
On 01/24/2014 02:07 PM, alexandros_e wrote:
With your help I found the solution. My DB was initially based on a 9.0
server and I had restored it on the 9.1 server. For some reason 9.0
fuzzystrmatch functions (levenstein...) were already present in this DB. So,
CREATE EXTENSION fuzzystrmatch did n
Hi All,
Could any one please confirm me in which community version "Fix multiple
bugs in index page locking during hot-standby WAL replay" has been fixed.
Your response in appreciated.
Warm Regards,
Abdul Sayeed
DBA - EnterpriseDB
Skype: abdul.sayeed24
On Sat, Jan 25, 2014 at 05:02:23AM +0530, Abdul Sayeed wrote:
> Hi All,
>
> Could any one please confirm me in which community version "Fix multiple bugs
> in index page locking during hot-standby WAL replay" has been fixed.
Well, that patch shows as being applied to 9.3.X on:
commit ebd
37 matches
Mail list logo
