> On 10 Jul 2024, at 06:58, Adrian Klaver wrote:
>
> On 7/9/24 17:46, Craig McIlwee wrote:
>> Full error message from earlier in the thread:
>> > psql:scripts/insert-addrs.sql:488: ERROR: syntax error at or near ";"
>> > LINE 488: ...2832,1,default,'85250 Red House Rd','Paisley','OR','97636');
On 7/9/24 17:46, Craig McIlwee wrote:
Full error message from earlier in the thread:
> psql:scripts/insert-addrs.sql:488: ERROR: syntax error at or near ";"
> LINE 488: ...2832,1,default,'85250 Red House Rd','Paisley','OR','97636');
>
On 7/10/24 06:44, Guyren Howe wrote:
>> On Jul 9, 2024, at 17:58, Krishnakant Mane wrote:
>>> Hello.
>>>
>>> I have a straight forward question, but I am just trying to analyze the
>>> specifics.
>>>
>>> So I have a set of queries depending on each other in a sequence to compute
>>> some resul
On 7/10/24 06:44, Guyren Howe wrote:
On Jul 9, 2024, at 17:58, Krishnakant Mane wrote:
Hello.
I have a straight forward question, but I am just trying to analyze the
specifics.
So I have a set of queries depending on each other in a sequence to compute
some results for generating financia
On Jul 9, 2024, at 17:58, Krishnakant Mane wrote:
>
> Hello.
>
> I have a straight forward question, but I am just trying to analyze the
> specifics.
>
> So I have a set of queries depending on each other in a sequence to compute
> some results for generating financial report.
>
> It involve
Hello.
I have a straight forward question, but I am just trying to analyze the
specifics.
So I have a set of queries depending on each other in a sequence to
compute some results for generating financial report.
It involves summing up some amounts from tuns or of rows and also on
certain c
Full error message from earlier in the thread:
> psql:scripts/insert-addrs.sql:488: ERROR: syntax error at or near ";"
> LINE 488: ...2832,1,default,'85250 Red House Rd','Paisley','OR','97636');
> ^
The error:
>
> LINE 488
On 7/9/24 15:40, Rich Shepard wrote:
On Tue, 9 Jul 2024, Adrian Klaver wrote:
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
Adrian,
It doesn't; it prints the contents of the file to th
On Tue, 9 Jul 2024, Rich Shepard wrote:
Should I run BEGIN: at the psql prompt prior to entering the insert
command? Would that tell me if any rows were entered and, if so, where
that stopped?
Began a transction, ran the script, checked the locations table for a couple
of rows to be inserted.
On Tue, 9 Jul 2024, Adrian Klaver wrote:
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
Adrian,
It doesn't; it prints the contents of the file to the virtual terminal.
Using my default s
On Tue, 9 Jul 2024, Ray O'Donnell wrote:
Did you run the entire thing inside a transaction? If so, then it will have
been rolled back after the error, and no rows will have been inserted.
Ray,
When I tried using transactions they froze the application. Probably because
I don't know to properl
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/inser
On 9 July 2024 23:14:33 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:scr
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
## Shenavai, Manuel (manuel.shena...@sap.com):
> Looking at autovacuum_vacuum_cost_delay:
> https://www.postgresql.org/docs/current/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY
>
> Can someone help to understand what a high or low value of this setting
> really means? Would it
Hi Shenvail,
Based on what I could understand,
Lower value will cause more frequent run of Autovacuum. Will have
less delay between processing data chunks but will put more load on the I/O
system. Autovacuum tasks will complete faster. Cleanup of dead tuples and
blots will be quicker thus increas
Hi everyone,
We are doing some tests with different autovacuum settings.
Looking at autovacuum_vacuum_cost_delay:
https://www.postgresql.org/docs/current/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY
Can someone help to understand what a high or low value of this setting really
On Mon, 2024-07-08 at 15:26 -0700, Joseph Hammerman wrote:
> In Postgres Weekly, I encountered this interesting article. The documentation
> on the use
> of AND CHAIN is here. A co-worker is interested in the difference between
> chaining
> and using the pipelining syntax.
>
> They look pretty s
On Tue, 2024-07-09 at 07:05 +0100, Jaurès FOUTE KUETE wrote:
> [image showing a large "pg_wal" directory]
>
> We are facing this issue and want to know how can I do to clean this folder
> without problem.
>
> What can be the cause of that ?
> and How can I clean this folder without stopping Logi
19 matches
Mail list logo
