Search Postgresql Archives

Re: COPY: row is too big

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: COPY: row is too big
From: doganmeh <mehmet@xxxxxxxxx>
Date: Sat, 27 May 2017 15:29:41 -0700 (MST)
Arc-authentication-results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of pgsql-general-owner+m231169=spinic=gmail.com@xxxxxxxxxxxxxx designates 2a02:16a8:dc51::56 as permitted sender) smtp.mailfrom=pgsql-general-owner+M231169=spinic=gmail.com@xxxxxxxxxxxxxx
Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:precedence:list-unsubscribe:list-subscribe:list-post :list-owner:list-id:list-help:list-archive:content-transfer-encoding :mime-version:subject:references:in-reply-to:message-id:to:from:date :arc-authentication-results; bh=2C9fdrKDyNOcs1c3/KGQF2w4NzsnKHPhNXWyqhz1ot0=; b=pkja+eOut/sVCZ+G1sm9+/BntaItRbakRp41mO2UfT4PI0I+wo0kk2AjmESdLUozvf c/4ebH+jIY5D3DelWdPJ0T4/IlXlvD/ANKcYCdqjaEuaWzjCXyTOE4SRFruiF3jAwDJP E7hT2hcs1SStJb0PwG1yr5twZhaYRi+GduzdbzWNPiGmXlwYWLbxIyFfnH/vZRI65DZe GHMSpLyVgyFIHRbDe6PyHCE/07HdlO307XcSoalNk5q1lLVWtJ3h1QwED0txNTysGdIb JxDgF7rbx+yAFxHciG1ZK8FEsgSxA0PhaL2xYAguOQVXCro7nPU5Kl/8yPKN6NNrqrJr afkw==
Arc-seal: i=1; a=rsa-sha256; t=1495924238; cv=none; d=google.com; s=arc-20160816; b=HypdlCP3h8vepB4unXkUt49xPED9j/qPZNui+RATsm/5W+STInQvr3q7YDtIFZhJYX I/NYfSQMlM/rnqv5SbVpvw5EJ+80BWE5NwJFyJwtywqyzF/Y2k3IQ0/O/5LG4Z7nXKUc L6OTMm471w1pb1vrzM3efF+9CFoLTlPRc8etwQQc4avVdY/Lt7yHDr+2oCDAtsXv/MhA BK/IgcdID1mFQP0tGM405pzMxZFCRdKwh40mLs2itTBIOpkEVOjY4uquFLkxGB+CK5tv R/w11+VlwfmAWlNkJq0MbELYqg8w/B2Gq07dplDNgHS5YIBFQ1rXyy1uDlfYetR2L8/C nq6A==
In-reply-to: <15552d1e-2098-124d-4c55-e98f146243c4@aklaver.com>
References: <F8E3E1D0-B51E-42A5-932B-4A110C2DD5E9@gmail.com> <CAAJSdji_8se1e_Rv1YK80xPx4wHShwrxY6NEkagiybAuDDUy6Q@mail.gmail.com> <15969913dd3.ea2ff58529997.7460368287916683127@zoho.com> <CAFj8pRBqv=Gd01zP_AtpdwnJkBk8dsMksa3NshhMTJZWvV7-+Q@mail.gmail.com> <68008319-bebf-b2a8-b503-f8c3aa42887e@aklaver.com> <CAEfWYyy5WXU__oRf0iMWthpRWZdJRNW2kt9v3da1BswtFKFP1Q@mail.gmail.com> <591360d9-00db-4e83-0feb-0b22109414f1@aklaver.com> <1596ea8639b.f2869ae91118.1165294942643742165@zoho.com> <1495800467776-5963385.post@n3.nabble.com> <15552d1e-2098-124d-4c55-e98f146243c4@aklaver.com>

Yes, csvkit is what I decided to go with. Thank you all!



--
View this message in context: http://www.postgresql-archive.org/COPY-row-is-too-big-tp5936997p5963559.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Re: COPY: row is too big
  - From: Rob Sargent
- Re: COPY: row is too big
  - From: John McKown
- Re: COPY: row is too big
  - From: vod vos
- Re: COPY: row is too big
  - From: Pavel Stehule
- Re: COPY: row is too big
  - From: Adrian Klaver
- Re: COPY: row is too big
  - From: Steve Crawford
- Re: COPY: row is too big
  - From: Adrian Klaver
- Re: COPY: row is too big
  - From: vod vos
- Re: COPY: row is too big
  - From: doganmeh
- Re: COPY: row is too big
  - From: Adrian Klaver

Prev by Date: Re: COPY: row is too big
Next by Date: Re: wal_retrieve_retry_interval
Previous by thread: Re: COPY: row is too big
Next by thread: Re: COPY: row is too big
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]