På torsdag 16. juni 2016 kl. 00:50:45, skrev Jeff Janes mailto:jeff.ja...@gmail.com>>:
On Wed, Jun 15, 2016 at 3:56 AM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: Hi.
First; Is this the correct forum to ask questions about the Postgres Pro's new
RUM-index?
If not, please point me
1. Stoped slon process on both provider and subscriber nodes
2. installed slony1-94-2.2.4-4.rhel5.x86_64 on both nodes
3. ran the script listed below
#!/bin/bash
/usr/pgsql-9.4/bin/slonik <<_EOF_
cluster name = slon_cluster_cmates;
node 1 admin conninfo = 'dbname=site host=site-db01.qs01.sea1.cmat
On Fri, Jun 17, 2016 at 5:36 AM, avi Singh
wrote:
> I am working on a project to upgrade postgresql from 9.4 to 9.5 we use
> slony for replication
>
>
> Phase 1 problem
>
> 1. We had slony version slony1-94-2.2.2-1.rhel5.x86_64 installed when i
> tried testing upgrade on my test env it failed coz
On Wed, Jun 15, 2016 at 12:49 AM, Catalin Maftei
wrote:
> hei Adrian,
>
> thx for your reply,
>
> this is an example:
>
> "CREATE OR REPLACE VIEW feedback.get_answers_set AS
> SELECT f.awb || '/' || r.dulapid as "awb",
> q.qid,
> q.question,
> a.aid,
> a.answer,
> q.questiona
On 6/15/2016 9:39 PM, Shaun Cutts wrote:
Is there a reason besides “its bad design” to disallow tables with many columns?
it would require significantly different internal architecture optimized
for said huge rows.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general
On 16/06/16 16:39, Shaun Cutts wrote:
The opinion of database developers is that using more than 1664 columns is bad
design, so that the current maximum number of columns is not onerous.
When I simply built applications on top of databases, I was of the same opinion.
However, now my job is to
Shaun Cutts writes:
> Is there a reason besides âits bad designâ to disallow tables with many
> columns?
There are numerous implementation problems you'd have to overcome.
There are illuminating comments in htup_details.h:
* MaxTupleAttributeNumber limits the number of (user) columns in a t
The opinion of database developers is that using more than 1664 columns is bad
design, so that the current maximum number of columns is not onerous.
When I simply built applications on top of databases, I was of the same opinion.
However, now my job is to perform some sort of analysis on data fr
hei Adrian,
thx for your reply,
this is an example:
"CREATE OR REPLACE VIEW feedback.get_answers_set AS
SELECT f.awb || '/' || r.dulapid as "awb",
q.qid,
q.question,
a.aid,
a.answer,
q.questionareid,
f.stamp_created
, c.first_name
, l.referinta_expeditor
FROM fe
On 06/16/2016 11:28 AM, Durgamahesh Manne wrote:
i can able to resolve the issue on migration from sql to postgres with
runmtk.sh without taking any support from edb
even i frustated with runmtk.sh as i wanted to use postgresql life long
in my company
For completeness and to help anyone else
I am working on a project to upgrade postgresql from 9.4 to 9.5 we use
slony for replication
Phase 1 problem
1. We had slony version slony1-94-2.2.2-1.rhel5.x86_64 installed when i
tried testing upgrade on my test env it failed coz slony 2.2.2 version is
not compatible with 9.5 so i upgraded sl
Please do not top-post.
On Thu, Jun 16, 2016 at 2:38 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Jun 16, 2016 at 2:21 PM, Liza Sazonova wrote:
>
>> Hello,
>>
>> I'm trying to implement a keyword-based search on my database.
>>
>> I have some text input (Say, "The A or B
Thank you!
It seems like this function's not available in PostgreSQL 9.5 that I'm
using
I'm getting: "ERROR: function tsvector_to_array(unknown) does not exist".
Do you know of any equivalent function in earlier releases?
I was thinking of casting ts_vector into text, and then splitting the te
On Thu, Jun 16, 2016 at 2:21 PM, Liza Sazonova wrote:
> Hello,
>
> I'm trying to implement a keyword-based search on my database.
>
> I have some text input (Say, "The A or B and C with D") and a list of
> keywords ("B","X","Y"). I want to identify which keywords are present in
> the text input.
i can able to resolve the issue on migration from sql to postgres with
runmtk.sh without taking any support from edb
even i frustated with runmtk.sh as i wanted to use postgresql life long in
my company
thank you for information
On Thu, Jun 16, 2016 at 11:43 PM, Durgamahesh Manne <
maheshpos
Hello,
I'm trying to implement a keyword-based search on my database.
I have some text input (Say, "The A or B and C with D") and a list of
keywords ("B","X","Y"). I want to identify which keywords are present in
the text input. I also want to use a thesaurus to process the text input,
since the
thank you for the information related to postgres
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi,
2016-06-16 9:48 GMT-03:00 Michael Paquier :
> On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués
> wrote:
>> El 16/06/16 a las 00:08, Michael Paquier escribió:
>>> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
>>> wrote:
How would the recovery process work? We expect the schema to
On Wed, 2016-06-15 at 15:56 +0200, Alexander Farber wrote:
> Good afternoon,
>
> at PostgreSQL 9.5.3 I have a stored function (full source code below)
> returning void, which I successfully call with PHP:
>
> function skipGame($dbh, $uid, $gid) {
> $sth = $dbh->prepare('SELECT words_skip_
Disclaimer: My company is a partner of EnterpriseDB and provides services
and consultation on EnterpriseDB tools
On Thu, 16 Jun 2016, 11:52 p.m. Neil Anderson,
wrote:
> On 2016-06-16 11:42 AM, Durgamahesh Manne wrote:
> > i got another error even i specified -targetdbtype
> > like
> > ./runMTK.s
On 2016-06-16 11:42 AM, Durgamahesh Manne wrote:
i got another error even i specified -targetdbtype
like
./runMTK.sh -sourcedbtype sqlserver -targetdbtype postgresql
-targetSchema public -schemaOnly -allTables dbo
Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
Source database connectiv
i already set password ..it appears when executing the runmtk.sh
jdbc already mentioned
On Thu, Jun 16, 2016 at 9:12 PM, Jan de Visser wrote:
>
> P L E A S E D O N ' T T O P P O S T
>
>
>
> On Thursday, June 1
i got another error even i specified -targetdbtype
like
./runMTK.sh -sourcedbtype sqlserver -targetdbtype postgresql -targetSchema
public -schemaOnly -allTables dbo
Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
Source database connectivity info...
conn =jdbc:jtds:sqlserver://fxserver.tr
P L E A S E D O N ' T T O P P O S T
On Thursday, June 16, 2016 9:00:48 PM EDT Durgamahesh Manne wrote:
> as per above conversation. i checked connectivity details as it is
> connected to database (even hostnam
On 06/16/2016 08:13 AM, Durgamahesh Manne wrote:
yes sir
as per above discussion..i already looked pdf postgres plus guide you
mentioned
as well as i already set password for postgres user associated with
postgres db
Is the Postgres server you are trying to connect to the Postgres
Advanced S
as per above conversation. i checked connectivity details as it is
connected to database (even hostname i mentioned connected to database)
psql --host 192.168.168.201 --user postgres -d raghu
Password for user postgres:
psql.bin (9.4.8, server 9.4.4)
Type "help" for help.
No entry for terminal
On 2016-06-16 11:13 AM, Durgamahesh Manne wrote:
yes sir
as per above discussion..i already looked pdf postgres plus guide you
mentioned
as well as i already set password for postgres user associated with
postgres db
On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne
mailto:maheshpostgr...@gma
Please don't top-post.
On Thursday, June 16, 2016 8:30:53 PM EDT Durgamahesh Manne wrote:
> hi
> sir
> as per above discussion same error repeated even mentioned ip address of
> hostname
>
> ./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
> -allTables dbo
>
>
> TARGET_DB_UR
yes sir
as per above discussion..i already looked pdf postgres plus guide you
mentioned
as well as i already set password for postgres user associated with
postgres db
On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:
> hi
> sir
> as per above discussion sam
hi
sir
as per above discussion same error repeated even mentioned ip address of
hostname
./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo
TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
TARGET_DB_USER=postgres
TARGET_DB_PASSWORD=*
Connecting w
Hello,
I am trying to copy a PostGIS database from one server to another using
pg_dump. This database uses pointcloud objects to store lidar points.
When I try to import the dump on the new machine, I get the following
errors:
2016-06-15 16:33:59 EDT LOG Pointcloud (1.1.0) module loaded at chara
On 06/16/2016 07:19 AM, Durgamahesh Manne wrote:
sir
PostgreSQL always no1 in world
as per above discussion
migration not working from sql to postgreSQL with runmtk.sh
Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting wit
sir
PostgreSQL always no1 in world
as per above discussion
migration not working from sql to postgreSQL with runmtk.sh
Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045:
On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:
>
> sir
>
> PostgreSQL always no1 in world
> as per above discussion
>
> migration not working from sql to postgreSQL with runmtk.sh
>
>
> Connecting with source SQL Server database server...
> Connected to Mi
On 06/15/2016 08:50 PM, Durgamahesh Manne wrote:
sir
as per above discussion .the URL which i mentioned in toolkit properties
was 100% correct .i have checked db connectivity from another cluster
with psql .connection esatblished to below mentioned database
conn =jdbc:postgresql://archive.trustf
El 16/06/16 a las 09:48, Michael Paquier escribió:
> On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués
> wrote:
>
>> This problem came up due to a difference between pg_dump on 9.1.12 and
>> 9.1.22 (I believe it was due to a patch on pg_dump that excluded the
>> dependent objects from being dumped
On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués wrote:
> El 16/06/16 a las 00:08, Michael Paquier escribió:
>> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
>> wrote:
>>>
>>> How would the recovery process work? We expect the schema to be there
>>> when restoring the tables?
>>
>> pg_dump crea
El 16/06/16 a las 00:08, Michael Paquier escribió:
> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
> wrote:
>>
>> How would the recovery process work? We expect the schema to be there
>> when restoring the tables?
>
> pg_dump creates the schema first via the CREATE EXTENSION command,
> then ta
38 matches
Mail list logo
