On 3/7/22 17:57, Rob Sargent wrote:
On 3/7/22 16:48, scott macri wrote:
[snip]
It pukes after the 9th column every time no matter what I
change.
COPY
option_details(a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y)
FROM '/home/dump
On 3/7/22 16:48, scott macri wrote:
On Mon, Mar 7, 2022, 6:42 PM Rob Sargent wrote:
On 3/7/22 16:33, scott macri wrote:
No luck
Bummer. Best to bottom post or in-line comment on this forum.
On Mon, Mar 7, 2022, 4:58 AM Rob Sargent
wrote:
On 3/7/22 02:08, S
On Mon, Mar 07, 2022 at 12:22:26PM -0500, Tom Lane wrote:
> Neither of those configurations fail for me, so either
> it's been fixed since 12.9, or (more likely) there is
> something to your test case beyond what you've mentioned.
Upgraded to 12.10 from pgdg, same problem.
> (I guess a long-shot
On 3/7/22 11:06 AM, Tom Lane wrote:
Jeff Ross writes:
Is there a way to get the DETAIL part as well?
It's not very well documented AFAICS, but a SPIError object has a
"detail" attribute, so "e.detail" should help you. It looks like
you might prefer to print "e.spidata", which seems to contain
Jeff Ross writes:
> With plpython (both u and 3u) all I see printed is the ERROR part.
> try:
> check = plpy.execute("delete from inspection where bundle_id in
> (select id from test_archive_20170401.load order by id)")
> except plpy.SPIError as e:
> plpy.notice("Erro
Hi,
On 2022-03-07 16:11:28 +0100, hubert depesz lubaczewski wrote:
> On Sun, Mar 06, 2022 at 11:10:00AM -0500, Tom Lane wrote:
> > > I tore these boxes down, so can't check immediately, but I think
> > > I remember that you're right - single-row queries didn't use JIT.
>
> Got focal box up. Loade
Hi all,
In psql a database error will print both ERROR: and DETAIL: lines.
postgres@testdb# delete from inspection where bundle_id in (select id
from test_archive_20170401.load order by id);
ERROR: update or delete on table "inspection" violates foreign key
constraint "inspection_weather_insp
hubert depesz lubaczewski writes:
> Got focal box up. Loaded schema for Pg.
> Initially select didn't break anything, but when I tuned down
> jit_above_cost so that it will kick in - got fails immediately.
Hmph. I tried two more builds:
* downgraded llvm to llvm-9, compiled PG 12 from source
*
On Sun, Mar 06, 2022 at 11:10:00AM -0500, Tom Lane wrote:
> > I tore these boxes down, so can't check immediately, but I think
> > I remember that you're right - single-row queries didn't use JIT.
Got focal box up. Loaded schema for Pg.
Initially select didn't break anything, but when I tuned dow
Thank you, Brent! You told me what I needed to know.
---
--
Susan E Hurst
Email: susan.hu...@brookhurstdata.com
Mobile: 314-486-3261
On 2022-03-06 19:35, Brent Wood wrote:
In line below...
On Monday, March 7, 2022, 05:36:34 AM GMT+13, Susan Hurst
wrote:
10 matches
Mail list logo
