Feedback-ID: i76984098:Fastmail
Message-ID: <71cf3e97-a0a5-4a94-add8-989cd1e2311d@aklaver.com>
Date: Tue, 9 Jul 2024 15:29:41 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Finding error in long input file
To: Rich Shepard <rshepard@appl-ecosys.com>, pgsql-general@postgresql.org
References: <b9639830-1a9-c1fc-8444-a436b167c56c@appl-ecosys.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <b9639830-1a9-c1fc-8444-a436b167c56c@appl-ecosys.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/71cf3e97-a0a5-4a94-add8-989cd1e2311d%40aklaver.com>
Precedence: bulk

On 7/9/24 15:14, Rich Shepard wrote:
> I've a file with 488 rows to be input into a table. I run the script using
> psql with the `\i' option.
> 
> After psql found a few missing commas I thought the script was clean. But,
> psql returned this error:
> bustrac=# \i scripts/insert-addrs.sql
> psql:scripts/insert-addrs.sql:488: ERROR:  syntax error at or near ";"
> LINE 488: ...2832,1,default,'85250 Red House Rd','Paisley','OR','97636');
>                                                                          
> ^ Am
> I correct that some rows were inserted into the table before this error was
> generated somewhere prior to the end of the file? If so, how do I determine
> which rows were inserted and what is the recommended procedure to locate
> just where that error is?
> 
> I've learned from experience that using the old coding approach of dividing
> the file in half, then half again and again until the row with the error is
> found produces multiple rows with different PKs. Not what I want to clean
> up.
> 
> A clue stick will be much appreciated.


bustrac=#\e scripts/insert-addrs.sql 488

If that raises this error:

environment variable PSQL_EDITOR_LINENUMBER_ARG must be set to specify a 
line number

then:

bustrac=#\e scripts/insert-addrs.sql

If the editor is vi then:

:488


> 
> TIA,
> 
> Rich
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com