Re: [GENERAL] syntax error

I have figured it out. Thanks for thinking -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] syntax error

Hi, I am setting up PostgreSQL standby on windows for the first time on version 9.4.14: Is the below syntax correct in the recovery.conf file restore_command = 'copy "D:\\apps\postgres\\pg_archivelog\\%f" "%p"' archive_cleanup_command = 'pg_archivecleanup "D:\\apps\postgres\pg_archivelog\\"

Re: [GENERAL] Syntax error needs fresh eyeballs

On Mon, 26 Dec 2016, Tom Lane wrote: ERROR: there is no unique constraint matching given keys for referenced table "weather_params". because Weather_Params.param isn't constrained to be unique. ... Seeing that Weather_Data also has a site_id column, I'm going to guess that what you wanted

Re: [GENERAL] Syntax error needs fresh eyeballs

From: Rich Shepard My schema includes three tables and psql throws an error I'm not seeing when I try to read the schema into the database. I'd appreciate fresh eyes looking at the table and learning what error I'm not seeing. The tables: CREATE TABLE Weather ( site_id INTEGER PRIMAR

Re: [GENERAL] Syntax error needs fresh eyeballs

Rich Shepard writes: >My schema includes three tables and psql throws an error I'm not seeing > when I try to read the schema into the database. I'd appreciate fresh eyes > looking at the table and learning what error I'm not seeing. Hm, seems straightforward enough to me: the only uniqueness

[GENERAL] Syntax error needs fresh eyeballs

My schema includes three tables and psql throws an error I'm not seeing when I try to read the schema into the database. I'd appreciate fresh eyes looking at the table and learning what error I'm not seeing. The tables: CREATE TABLE Weather ( site_id INTEGER PRIMARY KEY, site_name TEXT,

Re: [GENERAL] Syntax error for Function

On 01/20/2016 08:00 AM, Sachin Srivastava wrote: Dear Adiran, Thanks for your help !! First I want to say it's not giving the error for this ""languaget...@repos.birchstreet.net ", so there is any need to do the change as suggested by you. You are no

Re: [GENERAL] Syntax error for Function

Dear Adiran, Thanks for your help !! First I want to say it's not giving the error for this "" languaget...@repos.birchstreet.net", so there is any need to do the change as suggested by you. Second you suggested " exit with cur1; " - *You are right after putting the semi column my code is workin

Re: [GENERAL] Syntax error for Function

On 01/20/2016 06:32 AM, Sachin Srivastava wrote: Dear Thom, Please find the complete code as below and suggest now. I would suggest spending some time here: http://www.postgresql.org/docs/9.4/interactive/plpgsql.html in particular: http://www.postgresql.org/docs/9.4/interactive/plpgsql-cont

Re: [GENERAL] Syntax error for Function

Dear Thom, Please find the complete code as below and suggest now. -- -- Function: gen_budget_for_next_year(bigint, bigint, bigint) -- DROP FUNCTION gen_budget_for_next_year(bigint, bigint, bigint); CREATE OR REPLACE FUNCTION gen_budget_for_next_year( subid bigint, co

Re: [GENERAL] Syntax error for Function

On 20 January 2016 at 12:15, Sachin Srivastava wrote: > I am unable to find out the syntax error in below code, please suggest? > > > > ERROR: syntax error at or near "select" > LINE 44: select Count(0) into sFound from budget_period ... > ^ > ** Error **

[GENERAL] Syntax error for Function

I am unable to find out the syntax error in below code, please suggest? ERROR: syntax error at or near "select" LINE 44: select Count(0) into sFound from budget_period ... ^ ** Error ** ERROR: syntax error at or near "select" SQL state: 42601 Ch

Re: [GENERAL] syntax error while using pg_dump in Postgres 8.4

The psql console still operates mainly at the SQL level of input. You need to use your OS's shell to run pg_dump. Both psql and pg_dump are the same kind of application and are run in a similar fashion. David J. On Thu, Oct 30, 2014 at 11:13 AM, CrabbeS [via PostgreSQL] < ml-node+s1045698n5825

Re: [GENERAL] syntax error while using pg_dump in Postgres 8.4

CrabbeS wrote > I am trying to copy a table form one database to another by using this > command in the SQL-query builder: > pg_dump TA2000 -t from Forest -c -s | psql -h localhost postgis; pg_dump is a standalone application (i.e., something you run in a shell/command-line) and not an SQL command

[GENERAL] Syntax error at or near “on”

Hello! In PostgreSQL 8.4.13 why do I please get the syntax error ERROR: syntax error at or near "on" LINE: ... references balkan_users(id) check (id <> author) on delete ... for the following 2 statements? create table balkan_users ( id varchar(32) primary key, first_name varch

Re: [GENERAL] syntax error in a trigger. can't find it.

"Rhys A.D. Stewart" writes: > I must be very tired, very hungry or both. I'm getting a syntax error in > the last line with the 'END;' But am clearly not seeing what the error is. > Any help would be appreciated. I think you need to change ELSE IF to ELSEIF. As written you need two END IF lines

Re: [GENERAL] syntax error in a trigger. can't find it.

Found it, had ELSE IF instead of elsif..very from the indicated error. On Sat, Jan 12, 2013 at 5:10 PM, Rhys A.D. Stewart wrote: > Greetings, > > I must be very tired, very hungry or both. I'm getting a syntax error in > the last line with the 'END;' But am clearly not seeing what the error

[GENERAL] syntax error in a trigger. can't find it.

Greetings, I must be very tired, very hungry or both. I'm getting a syntax error in the last line with the 'END;' But am clearly not seeing what the error is. Any help would be appreciated. create or replace function dev.rqst_insrt() returns trigger as $_$

[GENERAL] syntax error collate

Hello If I do this from pgAdmin on windows to my localhost database 9.2 it works fine CREATE COLLATION Test ( LOCALE = 'en_US.UTF-8' ) If I connect to a linux server and do the sameI get ERROR: syntax error at or near "COLLATION" LINE 1: CREATE COLLATION Test ( On linux we have version strin

Re: [GENERAL] syntax error collate

On 03/10/2012 15:31, Niklas Langvig wrote: > Hello > If I do this from pgAdmin on windows to my localhost database 9.2 it > works fine > CREATE COLLATION Test ( > > LOCALE = 'en_US.UTF-8' > > ) > > > If I connect to a linux server and do the sameI get > > ERROR: syntax error at or near "C

Re: [GENERAL] Syntax Error for "boolean('value')" Type Casting

On May 22, 2011, at 6:22, Alban Hertroys wrote: > On 21 May 2011, at 21:17, David Johnston wrote: > >> SELECT boolean('true') >> SQL Error: ERROR: syntax error at or near "(" LINE 1: SELECT boolean('true') ^ >> >> The following work as expected: >> >> SEL

Re: [GENERAL] Syntax Error for "boolean('value')" Type Casting

On 21 May 2011, at 21:17, David Johnston wrote: > SELECT boolean('true') > >>> SQL Error: ERROR: syntax error at or near "(" >>> LINE 1: SELECT boolean('true') >>> ^ > > The following work as expected: > > SELECT bool('true') (...) > While I'm here.is there any downside t

[GENERAL] Syntax Error for "boolean('value')" Type Casting

PostgreSQL 9.0.3, compiled by Visual C++ build 1500, 64-bit The following intuitively valid statement fails: SELECT boolean('true') >>SQL Error: ERROR: syntax error at or near "(" >>LINE 1: SELECT boolean('true') >> ^ The following work as expected: SELEC

[GENERAL] Syntax error near returning

Hi Everyone, When I create a prepared statement like this in java (using JDBC): pStmt = conn.prepareStatement(qry); everything works ok. However when I want a scrollable resultset and use this: pStmt = conn.prepareStatement(qry,ResultSet.TYPE_SCROLL_INSENSITIVE); I get a syntax error: org.pos

Re: [GENERAL] Syntax error in spi_prepare usage

Thanks a lot Alban. That was simple! On Sat, Apr 24, 2010 at 10:15 PM, Alban Hertroys < dal...@solfertje.student.utwente.nl> wrote: > > If I remove the braces from (\$1, \$2, \$3) then it gives below error. > > > > my $query = (< > INSERT INTO changelogtest(id, txid, txtime) > > SELECT \$1,

Re: [GENERAL] Syntax error in spi_prepare usage

> If I remove the braces from (\$1, \$2, \$3) then it gives below error. > > my $query = (< INSERT INTO changelogtest(id, txid, txtime) > SELECT \$1, \$2, \$3 > EXCEPT > SELECT (id, txid, txtime) > FROM changelogtest > WHERE id = \$1 > AND txid = \$2 > AND txtime = \$3; > ENDQUE

[GENERAL] Syntax error in spi_prepare usage

I am using SPI_Prepare from trigger like below. I have some minor issue with $query syntax. I have tried almost all combination but I am not able to resolve. Could anyone please help me out. CREATE OR REPLACE FUNCTION insert_history_info() RETURNS VOID AS $BODY$ my $query = (< there is some issue

Re: [GENERAL] Syntax error in trigger

I got it resolved. I just need to put below statement into single quote instead of double quote. :) my $query ='INSERT INTO log_table(id) SELECT $1 EXCEPT SELECT id FROM log_table WHERE id = $1;'; Thanks, Jignesh On Thu, Apr 22, 2010 at 2:02 PM, Jignesh Shah wrote: > Thanks Anreas but I think t

Re: [GENERAL] Syntax error in trigger

Thanks Anreas but I think that's not a issue. The issue is something to do with "$1". I don't know how to get rid of it. techdb=# INSERT INTO log_table(id) SELECT 5 EXCEPT SELECT id FROM log_table WHERE id = 5; INSERT 0 1 techdb=# select * from log_table; id | txid | txtime +-

Re: [GENERAL] Syntax error in trigger

Jignesh Shah wrote: > Hi All, > > I have written below trigger and applied on the table but it is giving syntax > error when it gets invoked. Could you please help me what is wrong? I have > given complete details here: > > my trigger function: > > CREATE OR REPLACE FUNCTION techdb_logtable

[GENERAL] Syntax error in trigger

Hi All, I have written below trigger and applied on the table but it is giving syntax error when it gets invoked. Could you please help me what is wrong? I have given complete details here: *my trigger function:* ** CREATE OR REPLACE FUNCTION techdb_logtable_trigger() RETURNS trigger AS $BODY$

Re: [GENERAL] syntax error during function call

- From: Osvaldo Kussama [mailto:osvaldo.kuss...@gmail.com] Sent: Wednesday, January 27, 2010 11:57 AM To: Aycock, Jeff R. Subject: Re: [GENERAL] syntax error during function call 2010/1/27 Aycock, Jeff R. : > Hello, > > > > I have a function with three parameters that would populate

Re: [GENERAL] syntax error during function call

On Wed, Jan 27, 2010 at 10:40:17AM -0500, Aycock, Jeff R. wrote: > EXECUTE 'SELECT *, $1, now() INTO schema_1.'||whoami||' FROM > schema_2.'||whoami||' where created_dt between $2 and $3;' You'll also need to expand those other parameters. The code is executed in an independent scope and hence P

Re: [GENERAL] syntax error during function call

On 01/27/2010 08:50 AM, Aycock, Jeff R. wrote: Thanks for the catch. However, this did not fix the syntax error. Looking back at this thread I second Andreas's suggestion. It seems the syntax is right but the names are wrong. What is the result when you do SELECT * FROM schema_1.snapshot_ta

Re: [GENERAL] syntax error during function call

On 01/27/2010 08:50 AM, Aycock, Jeff R. wrote: Thanks for the catch. However, this did not fix the syntax error. You are sure the function is being replaced with versions that have the changes? In other words does \df+ show the changes? -- Adrian Klaver adrian.kla...@gmail.com -- Sent v

Re: [GENERAL] syntax error during function call

Thanks for the catch. However, this did not fix the syntax error. -Original Message- From: Adrian Klaver [mailto:adrian.kla...@gmail.com] Sent: Wednesday, January 27, 2010 11:47 AM To: Aycock, Jeff R. Cc: Pavel Stehule; pgsql-general@postgresql.org Subject: Re: [GENERAL] syntax error

Re: [GENERAL] syntax error during function call

On 01/27/2010 08:41 AM, Aycock, Jeff R. wrote: Adrian, I tried that as well and got the same error result. Regards, Jeff Aycock I went back to the original function and assuming no cut/paste errors there is a ';' missing after the last END. END; RETURN NEXT r; E

Re: [GENERAL] syntax error during function call

] syntax error during function call On 01/27/2010 08:27 AM, Aycock, Jeff R. wrote: > Pavel, > > Per your suggestion I modified one line below BEGIN to look like this: > > EXECUTE 'SELECT *, $1, now() INTO "schema_1".'||"whoami"||' FROM > "s

Re: [GENERAL] syntax error during function call

Aycock, Jeff R. wrote: > Pavel, > > Per your suggestion I modified one line below BEGIN to look like this: > > EXECUTE 'SELECT *, $1, now() INTO "schema_1".'||"whoami"||' FROM > "schema_2".'||"whoami"||' where created_dt between $2 and $3;' ^^

Re: [GENERAL] syntax error during function call

On 01/27/2010 08:27 AM, Aycock, Jeff R. wrote: Pavel, Per your suggestion I modified one line below BEGIN to look like this: EXECUTE 'SELECT *, $1, now() INTO "schema_1".'||"whoami"||' FROM "schema_2".'||"whoami"||' where created_dt between $2 and $3;' However, it is still giving me the same

Re: [GENERAL] syntax error during function call

s still giving me the same syntax error as before. I must be missing something here though. Thanks for the suggestion, however. Regards, Jeff Aycock -Original Message- From: Pavel Stehule [mailto:pavel.steh...@gmail.com] Sent: Wednesday, January 27, 2010 11:13 AM To: Aycock, Jeff R

Re: [GENERAL] syntax error during function call

> > ERROR:  syntax error at or near "(" > > LINE 1: SELECT *, $1, now() INTO schema_1.(table_A) FROM schema_2.(table_A) > where created_dt between $2 and $3; > > schema_1.(table_A) is nonsense. have to be "schema_1"."table_A" regards Pavel Stehule -- Sent via pgsql-general mailing list (pgsql-g

Re: [GENERAL] syntax error during function call

010 11:00 AM To: Aycock, Jeff R. Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] syntax error during function call On 27/01/2010 15:40, Aycock, Jeff R. wrote: > BEGIN > > FOR r IN SELECT * FROM schema_1.snapshot_table > > LOOP > > > > DE

Re: [GENERAL] syntax error during function call

On 27/01/2010 15:40, Aycock, Jeff R. wrote: > BEGIN > > FOR r IN SELECT * FROM schema_1.snapshot_table > > LOOP > > > > DECLARE whoami text := r; I could be wrong, but I don't think that the DECLARE inside the loop is correct. I think you have to declare "whoami" with t

[GENERAL] syntax error during function call

Hello, I have a function with three parameters that would populate a table in one schema from another table of the same name in another schema. The tables are dynamically selected at execution time. CREATE OR REPLACE FUNCTION schema_1.getAllSnapShot(user_id text, begin_dt date, end_dt date

Re: [GENERAL] Syntax error with select statement

Thank You, Aravind. --- On Thu, 12/18/08, Joshua J. Kugler wrote: From: Joshua J. Kugler Subject: Re: [GENERAL] Syntax error with select statement To: pgsql-general@postgresql.org Date: Thursday, December 18, 2008, 1:51 AM On Wednesday 17 December 2008, justin said something like: > aravi

Re: [GENERAL] Syntax error with select statement

On Wednesday 17 December 2008, justin said something like: > aravind chandu wrote: > > Hello, > > I have problem with select statement in c++ program I am > > using pqxx library to connect to postgresql database.My query is > > > > result R(T.exec(" select * from dbtable where u

Re: [GENERAL] Syntax error with select statement

aravind chandu wrote: Hello, I have problem with select statement in c++ program I am using pqxx library to connect to postgresql database.My query is result R(T.exec(" select * from dbtable where username = ' "+user+" ' and password = ' "+st+" ' ")); here st i

[GENERAL] Syntax error with select statement

Hello, I have problem with select statement in c++ program I am using pqxx library to connect to postgresql database.My query is result R(T.exec(" select * from dbtable where username = ' "+user+" ' and password = ' "+st+" ' ")); here st is in encrypted format

Re: [GENERAL] syntax error on: GET DIAGNOSTICS xcount = ROW_COUNT;

<[EMAIL PROTECTED]> writes: > I am getting an error on "GET DIAGNOSTICS " statement in a PL/SQL function > below. > CREATE OR REPLACE FUNCTION test(lid int, OUT nid int) AS $$ > DECLARE > road_row road%ROWTYPE; > BEGIN > SELECT * INTO road_row FROM road WHERE link_id=lid; > GET DIAGNOSTICS

[GENERAL] syntax error on: GET DIAGNOSTICS xcount = ROW_COUNT;

Hi All, I am getting an error on "GET DIAGNOSTICS " statement in a PL/SQL function below. CREATE OR REPLACE FUNCTION test(lid int, OUT nid int) AS $$ DECLARE road_row road%ROWTYPE; BEGIN SELECT * INTO road_row FROM road WHERE link_id=lid; GET DIAGNOSTICS xcount = ROW_COUNT; IF xcount = 0

Re: [GENERAL] syntax error at or near "PERFORM"

On 15/08/2008 05:32, Dale wrote: On Aug 15, 2:14 pm, Dale <[EMAIL PROTECTED]> wrote: even when I try executing something basic: PERFORM (2 + 3); I found my problem. Unfortunately PERFORM can only be used within a "LANGUAGE plpgsql" script. Yes, that's it - outside a function, you just d

Re: [GENERAL] syntax error at or near "PERFORM"

On Aug 15, 2:14 pm, Dale <[EMAIL PROTECTED]> wrote: > Hi, > > When ever I try and call the PERFORM statement I get: > ERROR:  syntax error at or near "PERFORM" > even when I try executing something basic:  PERFORM (2 + 3); > > Any ideas please? > > Dale. I found my problem. Unfortunately PERFORM

[GENERAL] syntax error at or near "PERFORM"

Hi, When ever I try and call the PERFORM statement I get: ERROR: syntax error at or near "PERFORM" even when I try executing something basic: PERFORM (2 + 3); Any ideas please? Dale. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: h

Re: [GENERAL] syntax error with execute

> EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES > ('||vals||') RETURNING currval('''||seqname||''')' INTO newid > > Note where last quote goes. That was exactly what I wanted to do! SELECT 'Thank you' FROM heart; -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org

Re: [GENERAL] syntax error with execute

On Fri, May 30, 2008 at 9:25 PM, A B <[EMAIL PROTECTED]> wrote: > I have a query like this in a plpgsql function: > > EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES > ('||vals||') RETURNING currval('''||seqname||''') INTO newid' > > and I get the response: > > ERROR: syntax error at o

Re: [GENERAL] syntax error with execute

I haven't use the RETURNING clause before, but the "INTO" option, at least in SELECT sentences, must be outside of the string expression. This way: EXECUTE 'some query' INTO variable; Cheers. 2008/5/30 A B <[EMAIL PROTECTED]>: > I have a query like this in a plpgsql function: > > EXECUTE 'INSERT

Re: [GENERAL] syntax error with execute

> > EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES > > ('||vals||') RETURNING currval('''||seqname||''') INTO newid' You probably were to do: EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES ('||vals||') RETURNING currval('''||seqname||''')' INTO newid Note where last quo

Re: [GENERAL] syntax error with execute

Pretty sure you have to create the query as a string and execute that. On Fri, May 30, 2008 at 9:55 AM, A B <[EMAIL PROTECTED]> wrote: > I have a query like this in a plpgsql function: > > EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES > ('||vals||') RETURNING currval('''||seqname||'''

[GENERAL] syntax error with execute

I have a query like this in a plpgsql function: EXECUTE 'INSERT INTO '||tablename||' ('||fields||') VALUES ('||vals||') RETURNING currval('''||seqname||''') INTO newid' and I get the response: ERROR: syntax error at or near "INTO" LINE 1: ...','2008','4',NULL) RETURNING currval('id_seq') INTO n

Re: [GENERAL] Syntax error when restoring database from dump

My mistake. Sorry for the noise. Regards, Clodoaldo 2008/4/12, Clodoaldo <[EMAIL PROTECTED]>: > I dumped the db with: > pg_dump -C -f dbname.dump > > $ uname -a > Linux myhost.mydomain.net 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 14:10:25 > EST 2007 x86_64 x86_64 x86_64 GNU/Linux > > Postgresql 8.

[GENERAL] Syntax error when restoring database from dump

I dumped the db with: pg_dump -C -f dbname.dump $ uname -a Linux myhost.mydomain.net 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 14:10:25 EST 2007 x86_64 x86_64 x86_64 GNU/Linux Postgresql 8.2.7 And restored in another machine: $ uname -a Linux dkt 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:54:46 EDT 2008 i686

Re: [GENERAL] syntax error at or near "PROCEDURAL"

be problems. But it seems > so. I will give it a try an report the result. > > Thanks Andreas > > -Ursprüngliche Nachricht- > Von: Magnus Hagander [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 26. Februar 2008 10:30 > An: Andreas Lau; pgsql-general@postgresql.org

Re: [GENERAL] syntax error at or near "PROCEDURAL"

s Hagander [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 26. Februar 2008 10:30 An: Andreas Lau; pgsql-general@postgresql.org Betreff: Re: [GENERAL] syntax error at or near "PROCEDURAL" On Tue, Feb 26, 2008 at 10:26:25AM +0100, Martijn van Oosterhout wrote: > On Tue, Feb 26, 2008 at 1

Re: [GENERAL] syntax error at or near "PROCEDURAL"

On Tue, Feb 26, 2008 at 10:26:25AM +0100, Martijn van Oosterhout wrote: > On Tue, Feb 26, 2008 at 10:23:05AM +0100, Magnus Hagander wrote: > > Any chance you are running pg_dump/pg_restore version 8.3? The syntax > > appears to be what 8.3 uses, not 8.3.. > > > > You can use (and should use) an 8.

Re: [GENERAL] syntax error at or near "PROCEDURAL"

On Tue, Feb 26, 2008 at 10:23:05AM +0100, Magnus Hagander wrote: > Any chance you are running pg_dump/pg_restore version 8.3? The syntax > appears to be what 8.3 uses, not 8.3.. > > You can use (and should use) an 8.3 pg_dump to dump your 8.2 database when > upgrading to 8.3, but you often can't r

Re: [GENERAL] syntax error at or near "PROCEDURAL"

On Mon, Feb 25, 2008 at 06:40:43PM +0100, Andreas Lau wrote: > Hello, > > I try to restore a dump file on a new Database. But unfortunatly i get this > error: > > pg_restore: [archiver (db)] Error while PROCESSING TOC: > pg_restore: [archiver (db)] Error from TOC entry 532; 2612 16386 PROCEDUR

[GENERAL] syntax error at or near "PROCEDURAL"

Hello, I try to restore a dump file on a new Database. But unfortunatly i get this error: pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 532; 2612 16386 PROCEDURAL LANGUAGE plpgsql postgres pg_restore: [archiver (db)] could not execute

Re: [GENERAL] Syntax error in a large COPY

Andrej Ricnik-Bay wrote: > On 11/8/07, Collin Kidder <[EMAIL PROTECTED]> wrote: > > > I'm with Thomas. I think that, while inline posting is a good thing, > > bottom posting is dead stupid and wastes my time. > Just as bad as top-posting, really. > > > It is far easier to > > follow a thread with

Re: [GENERAL] Syntax error in a large COPY

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/07/07 11:35, Andrej Ricnik-Bay wrote: > On 11/8/07, Collin Kidder <[EMAIL PROTECTED]> wrote: [snip] > > >> No, just not everyone agrees with your viewpoint on this topic. Top >> posting has it's place and some of us prefer it. > But they could

Re: [GENERAL] Syntax error in a large COPY

Collin Kidder wrote: I'm with Thomas. I think that, while inline posting is a good thing, bottom posting is dead stupid and wastes my time. It is far easier to follow a thread with top posting as the relevant text is right there at the top ready to be read. That sounds more like an argument t

Re: [GENERAL] Syntax error in a large COPY

On 11/8/07, Collin Kidder <[EMAIL PROTECTED]> wrote: > I'm with Thomas. I think that, while inline posting is a good thing, > bottom posting is dead stupid and wastes my time. Just as bad as top-posting, really. > It is far easier to > follow a thread with top posting as the relevant text is righ

Re: [GENERAL] Syntax error in a large COPY

My point is: with top-posting I don't care how many lines were repeated because I don't have to scroll. Considering there is an RFC that recommends inline posting over top-posting (http://tools.ietf.org/html/rfc1855), and considering the fact that this topic has been beat to death on do

Re: [GENERAL] Syntax error in a large COPY

In response to Thomas Kellerer <[EMAIL PROTECTED]>: > Tom Lane, 07.11.2007 06:14: > > Thomas Kellerer <[EMAIL PROTECTED]> writes: > >> If everyone simply top-posted, there would be no need for me to scroll > >> down, > >> just to find a two line answer below a forty line quote - which I > >> pe

Re: [GENERAL] Syntax error in a large COPY

Reg Me Please wrote: > P.S. > Why not including the pgloader into the main tarball? We are not attempting to include every useful tool in the database server. We're actually moving in the opposite direction: stuff has been offloaded to pgfoundry as appropriate. Add-on packages are encouraged. If

Re: [GENERAL] Syntax error in a large COPY

Le mercredi 07 novembre 2007, Reg Me Please a écrit : > I installed .deb. The man page has not been included. It seems the latter package on pgfoundry does have a problem here. As I have some patches waiting for a release, I'll make current CVS the 2.2.2 version and update the pgfoundry files so

Re: [GENERAL] Syntax error in a large COPY

Il Tuesday 06 November 2007 19:05:52 Reg Me Please ha scritto: > Hi all. > I'm generating an SQL script to load some million rows into a table. > I'm trying to use the COPY command in order to speed the load up. > > At a certain point I get an error telling about a > "invalid input syntax for type

Re: [GENERAL] Syntax error in a large COPY

Il Wednesday 07 November 2007 11:26:56 Dimitri Fontaine ha scritto: > Le mercredi 07 novembre 2007, Reg Me Please a écrit : > > Maybe just a complete example would suffice. Let's say a table structure, > > a CSV and a raw text file, a config file and the run output. > > Do you mean something like t

Re: [GENERAL] Syntax error in a large COPY

Le mercredi 07 novembre 2007, Reg Me Please a écrit : > Maybe just a complete example would suffice. Let's say a table structure, a > CSV and a raw text file, a config file and the run output. Do you mean something like the included examples, which I tend to also use as (regression) tests? http

Re: [GENERAL] Syntax error in a large COPY

Il Wednesday 07 November 2007 11:10:40 Dimitri Fontaine ha scritto: > Le mercredi 07 novembre 2007, Reg Me Please a écrit : > > pgloader seems not that easy to use for a newbie like myself. > > Also because domentation seems too skinny. > > Sorry about this, writting documentation in English is not

Re: [GENERAL] Syntax error in a large COPY

Le mercredi 07 novembre 2007, Reg Me Please a écrit : > pgloader seems not that easy to use for a newbie like myself. > Also because domentation seems too skinny. Sorry about this, writting documentation in English is not that easy when it's not one's natural language... I'll accept any comment/p

Re: [GENERAL] Syntax error in a large COPY

Il Wednesday 07 November 2007 07:54:41 Reg Me Please ha scritto: > Il Wednesday 07 November 2007 01:29:44 Alvaro Herrera ha scritto: > > Reg Me Please wrote: > > > Il Tuesday 06 November 2007 22:13:15 hai scritto: > > > That's the "branch and bound". Editing 29M+ lines file takes some time. > > > B

Re: [GENERAL] Syntax error in a large COPY

Tom Lane, 07.11.2007 06:14: Thomas Kellerer <[EMAIL PROTECTED]> writes: If everyone simply top-posted, there would be no need for me to scroll down, just to find a two line answer below a forty line quote - which I personally find more irritating than top-posting. I think you're ignoring my b

Re: [GENERAL] Syntax error in a large COPY

Il Wednesday 07 November 2007 01:29:44 Alvaro Herrera ha scritto: > Reg Me Please wrote: > > Il Tuesday 06 November 2007 22:13:15 hai scritto: > > That's the "branch and bound". Editing 29M+ lines file takes some time. > > But this is the way I'm going to go right now. > > Huh, why not just use pgl

Re: [GENERAL] Syntax error in a large COPY

Thomas Kellerer <[EMAIL PROTECTED]> writes: > If everyone simply top-posted, there would be no need for me to scroll down, > just to find a two line answer below a forty line quote - which I personally > find more irritating than top-posting. I think you're ignoring my basic point, which was tha

Re: [GENERAL] Syntax error in a large COPY

Reg Me Please wrote: > Il Tuesday 06 November 2007 22:13:15 hai scritto: > > Split it in half, with the appropriate sql on each end so the data > > still works, and see which half causes a problem. Keep splitting the > > one that causes a problem in half until you have a small one with the > > pr

Re: [GENERAL] Syntax error in a large COPY

Hi, Le Tuesday 06 November 2007 22:40:50 Tom Lane, vous avez écrit : > Reg Me Please <[EMAIL PROTECTED]> writes: > > I'm trying to understand what and where. > > The point is that I have this 29M+ lines script telling me there's a > > problem somewhere. You could use pgloader, which reads CSV inp

Re: [GENERAL] Syntax error in a large COPY

Tom Lane wrote on 06.11.2007 21:21: The real point here is that when writing to a mailing list, you should make an effort to conserve other peoples' time. Hundreds of people are going to read what you wrote, possibly thousands when you count in people searching the list archives in the future.

Re: [GENERAL] Syntax error in a large COPY

Il Tuesday 06 November 2007 22:37:12 Scott Marlowe ha scritto: > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > Il Tuesday 06 November 2007 22:13:15 hai scritto: > > > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > > > Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritt

Re: [GENERAL] Syntax error in a large COPY

Reg Me Please <[EMAIL PROTECTED]> writes: > I'm trying to understand what and where. > The point is that I have this 29M+ lines script telling me there's a problem > somewhere. It told you exactly where it detected the problem. Actually ... are you looking at the right error message? If this is

Re: [GENERAL] Syntax error in a large COPY

On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > Il Tuesday 06 November 2007 22:13:15 hai scritto: > > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > > Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritto: > > > > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > > >

Re: [GENERAL] Syntax error in a large COPY

Il Tuesday 06 November 2007 22:13:15 hai scritto: > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritto: > > > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > > > That seems not to be the case. > > > > The last line has a \

Re: [GENERAL] Syntax error in a large COPY

On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritto: > > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > > That seems not to be the case. > > > The last line has a \. by its own and the last but one is > > > well formed. > >

Re: [GENERAL] Syntax error in a large COPY

Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritto: > On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > > That seems not to be the case. > > The last line has a \. by its own and the last but one is > > well formed. > > (Please don't top post...) > > Got a self contained test case y

Re: [GENERAL] Syntax error in a large COPY

"Scott Marlowe" <[EMAIL PROTECTED]> writes: > But the other reason is that top posters are often the biggest > offenders of not editing their replies. there's nothing like seeing a > one line reply to a 500 line conversation. > When inline posting, one can delete the parts of the converstation > t

Re: [GENERAL] Syntax error in a large COPY

On Nov 6, 2007 1:16 PM, Collin Kidder <[EMAIL PROTECTED]> wrote: > This is offtopic but there is nothing wrong with top posting. Is there a > mail list policy on it or are you just picky about it? OK, I was being a bit flippant with my last response. The reasoning on technical mailing lists for p

Re: [GENERAL] Syntax error in a large COPY

A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? On Nov 6, 2007 1:16 PM, Collin Kidder <[EMAIL PROTECTED]> wrote: > This is offtopic but there is nothing wrong with top postin

Re: [GENERAL] Syntax error in a large COPY

This is offtopic but there is nothing wrong with top posting. Is there a mail list policy on it or are you just picky about it? Scott Marlowe wrote: On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: That seems not to be the case. The last line has a \. by its own and the last but one is

Re: [GENERAL] Syntax error in a large COPY

On 11/6/07, Reg Me Please <[EMAIL PROTECTED]> wrote: > That seems not to be the case. > The last line has a \. by its own and the last but one is > well formed. (Please don't top post...) Got a self contained test case you can post? ---(end of broadcast)--

Re: [GENERAL] Syntax error in a large COPY

That seems not to be the case. The last line has a \. by its own and the last but one is well formed. Il Tuesday 06 November 2007 19:14:00 Tom Lane ha scritto: > Reg Me Please <[EMAIL PROTECTED]> writes: > > At a certain point I get an error telling about a > > "invalid input syntax for type numer

  1   2   >