1COPY(7) PostgreSQL 14.3 Documentation COPY(7)
2
6 COPY - copy data between a file and a table
7
9 COPY table_name [ ( column_name [, ...] ) ]
10 FROM { 'filename' | PROGRAM 'command' | STDIN }
11 [ [ WITH ] ( option [, ...] ) ]
12 [ WHERE condition ]
13 COPY { table_name [ ( column_name [, ...] ) ] | ( query ) }
15 TO { 'filename' | PROGRAM 'command' | STDOUT }
16 [ [ WITH ] ( option [, ...] ) ]
17 where option can be one of:
19 FORMAT format_name
21 FREEZE [ boolean ]
22 DELIMITER 'delimiter_character'
23 NULL 'null_string'
24 HEADER [ boolean ]
25 QUOTE 'quote_character'
26 ESCAPE 'escape_character'
27 FORCE_QUOTE { ( column_name [, ...] ) | * }
28 FORCE_NOT_NULL ( column_name [, ...] )
29 FORCE_NULL ( column_name [, ...] )
30 ENCODING 'encoding_name'
31
33 COPY moves data between PostgreSQL tables and standard file-system
34 files. COPY TO copies the contents of a table to a file, while COPY
35 FROM copies data from a file to a table (appending the data to whatever
36 is in the table already). COPY TO can also copy the results of a
37 SELECT query.
38 If a column list is specified, COPY TO copies only the data in the
40 specified columns to the file. For COPY FROM, each field in the file is
41 inserted, in order, into the specified column. Table columns not
42 specified in the COPY FROM column list will receive their default
43 values.
44 COPY with a file name instructs the PostgreSQL server to directly read
46 from or write to a file. The file must be accessible by the PostgreSQL
47 user (the user ID the server runs as) and the name must be specified
48 from the viewpoint of the server. When PROGRAM is specified, the server
49 executes the given command and reads from the standard output of the
50 program, or writes to the standard input of the program. The command
51 must be specified from the viewpoint of the server, and be executable
52 by the PostgreSQL user. When STDIN or STDOUT is specified, data is
53 transmitted via the connection between the client and the server.
54 Each backend running COPY will report its progress in the
56 pg_stat_progress_copy view. See Section 28.4.6 for details.
57
59 table_name
60 The name (optionally schema-qualified) of an existing table.
61 column_name
63 An optional list of columns to be copied. If no column list is
64 specified, all columns of the table except generated columns will
65 be copied.
66 query
68 A SELECT, VALUES, INSERT, UPDATE, or DELETE command whose results
69 are to be copied. Note that parentheses are required around the
70 query.
71 For INSERT, UPDATE and DELETE queries a RETURNING clause must be
73 provided, and the target relation must not have a conditional rule,
74 nor an ALSO rule, nor an INSTEAD rule that expands to multiple
75 statements.
76 filename
78 The path name of the input or output file. An input file name can
79 be an absolute or relative path, but an output file name must be an
80 absolute path. Windows users might need to use an E'' string and
81 double any backslashes used in the path name.
82 PROGRAM
84 A command to execute. In COPY FROM, the input is read from standard
85 output of the command, and in COPY TO, the output is written to the
86 standard input of the command.
87 Note that the command is invoked by the shell, so if you need to
89 pass any arguments to shell command that come from an untrusted
90 source, you must be careful to strip or escape any special
91 characters that might have a special meaning for the shell. For
92 security reasons, it is best to use a fixed command string, or at
93 least avoid passing any user input in it.
94 STDIN
96 Specifies that input comes from the client application.
97 STDOUT
99 Specifies that output goes to the client application.
100 boolean
102 Specifies whether the selected option should be turned on or off.
103 You can write TRUE, ON, or 1 to enable the option, and FALSE, OFF,
104 or 0 to disable it. The boolean value can also be omitted, in which
105 case TRUE is assumed.
106 FORMAT
108 Selects the data format to be read or written: text, csv (Comma
109 Separated Values), or binary. The default is text.
110 FREEZE
112 Requests copying the data with rows already frozen, just as they
113 would be after running the VACUUM FREEZE command. This is intended
114 as a performance option for initial data loading. Rows will be
115 frozen only if the table being loaded has been created or truncated
116 in the current subtransaction, there are no cursors open and there
117 are no older snapshots held by this transaction. It is currently
118 not possible to perform a COPY FREEZE on a partitioned table.
119 Note that all other sessions will immediately be able to see the
121 data once it has been successfully loaded. This violates the normal
122 rules of MVCC visibility and users specifying should be aware of
123 the potential problems this might cause.
124 DELIMITER
126 Specifies the character that separates columns within each row
127 (line) of the file. The default is a tab character in text format,
128 a comma in CSV format. This must be a single one-byte character.
129 This option is not allowed when using binary format.
130 NULL
132 Specifies the string that represents a null value. The default is
133 \N (backslash-N) in text format, and an unquoted empty string in
134 CSV format. You might prefer an empty string even in text format
135 for cases where you don't want to distinguish nulls from empty
136 strings. This option is not allowed when using binary format.
137 Note
139 When using COPY FROM, any data item that matches this string
140 will be stored as a null value, so you should make sure that
141 you use the same string as you used with COPY TO.
142 HEADER
144 Specifies that the file contains a header line with the names of
145 each column in the file. On output, the first line contains the
146 column names from the table, and on input, the first line is
147 ignored. This option is allowed only when using CSV format.
148 QUOTE
150 Specifies the quoting character to be used when a data value is
151 quoted. The default is double-quote. This must be a single one-byte
152 character. This option is allowed only when using CSV format.
153 ESCAPE
155 Specifies the character that should appear before a data character
156 that matches the QUOTE value. The default is the same as the QUOTE
157 value (so that the quoting character is doubled if it appears in
158 the data). This must be a single one-byte character. This option is
159 allowed only when using CSV format.
160 FORCE_QUOTE
162 Forces quoting to be used for all non-NULL values in each specified
163 column. NULL output is never quoted. If * is specified, non-NULL
164 values will be quoted in all columns. This option is allowed only
165 in COPY TO, and only when using CSV format.
166 FORCE_NOT_NULL
168 Do not match the specified columns' values against the null string.
169 In the default case where the null string is empty, this means that
170 empty values will be read as zero-length strings rather than nulls,
171 even when they are not quoted. This option is allowed only in COPY
172 FROM, and only when using CSV format.
173 FORCE_NULL
175 Match the specified columns' values against the null string, even
176 if it has been quoted, and if a match is found set the value to
177 NULL. In the default case where the null string is empty, this
178 converts a quoted empty string into NULL. This option is allowed
179 only in COPY FROM, and only when using CSV format.
180 ENCODING
182 Specifies that the file is encoded in the encoding_name. If this
183 option is omitted, the current client encoding is used. See the
184 Notes below for more details.
185 WHERE
187 The optional WHERE clause has the general form
188 WHERE condition
190 where condition is any expression that evaluates to a result of
192 type boolean. Any row that does not satisfy this condition will not
193 be inserted to the table. A row satisfies the condition if it
194 returns true when the actual row values are substituted for any
195 variable references.
196 Currently, subqueries are not allowed in WHERE expressions, and the
198 evaluation does not see any changes made by the COPY itself (this
199 matters when the expression contains calls to VOLATILE functions).
200
202 On successful completion, a COPY command returns a command tag of the
203 form
204 COPY count
206 The count is the number of rows copied.
208 Note
210 psql will print this command tag only if the command was not COPY
211 ... TO STDOUT, or the equivalent psql meta-command \copy ... to
212 stdout. This is to prevent confusing the command tag with the data
213 that was just printed.
214
216 COPY TO can be used only with plain tables, not views, and does not
217 copy rows from child tables or child partitions. For example, COPY
218 table TO copies the same rows as SELECT * FROM ONLY table. The syntax
219 COPY (SELECT * FROM table) TO ... can be used to dump all of the rows
220 in an inheritance hierarchy, partitioned table, or view.
221 COPY FROM can be used with plain, foreign, or partitioned tables or
223 with views that have INSTEAD OF INSERT triggers.
224 You must have select privilege on the table whose values are read by
226 COPY TO, and insert privilege on the table into which values are
227 inserted by COPY FROM. It is sufficient to have column privileges on
228 the column(s) listed in the command.
229 If row-level security is enabled for the table, the relevant SELECT
231 policies will apply to COPY table TO statements. Currently, COPY FROM
232 is not supported for tables with row-level security. Use equivalent
233 INSERT statements instead.
234 Files named in a COPY command are read or written directly by the
236 server, not by the client application. Therefore, they must reside on
237 or be accessible to the database server machine, not the client. They
238 must be accessible to and readable or writable by the PostgreSQL user
239 (the user ID the server runs as), not the client. Similarly, the
240 command specified with PROGRAM is executed directly by the server, not
241 by the client application, must be executable by the PostgreSQL user.
242 COPY naming a file or command is only allowed to database superusers or
243 users who are granted one of the roles pg_read_server_files,
244 pg_write_server_files, or pg_execute_server_program, since it allows
245 reading or writing any file or running a program that the server has
246 privileges to access.
247 Do not confuse COPY with the psql instruction \copy. \copy invokes
249 COPY FROM STDIN or COPY TO STDOUT, and then fetches/stores the data in
250 a file accessible to the psql client. Thus, file accessibility and
251 access rights depend on the client rather than the server when \copy is
252 used.
253 It is recommended that the file name used in COPY always be specified
255 as an absolute path. This is enforced by the server in the case of COPY
256 TO, but for COPY FROM you do have the option of reading from a file
257 specified by a relative path. The path will be interpreted relative to
258 the working directory of the server process (normally the cluster's
259 data directory), not the client's working directory.
260 Executing a command with PROGRAM might be restricted by the operating
262 system's access control mechanisms, such as SELinux.
263 COPY FROM will invoke any triggers and check constraints on the
265 destination table. However, it will not invoke rules.
266 For identity columns, the COPY FROM command will always write the
268 column values provided in the input data, like the INSERT option
269 OVERRIDING SYSTEM VALUE.
270 COPY input and output is affected by DateStyle. To ensure portability
272 to other PostgreSQL installations that might use non-default DateStyle
273 settings, DateStyle should be set to ISO before using COPY TO. It is
274 also a good idea to avoid dumping data with IntervalStyle set to
275 sql_standard, because negative interval values might be misinterpreted
276 by a server that has a different setting for IntervalStyle.
277 Input data is interpreted according to ENCODING option or the current
279 client encoding, and output data is encoded in ENCODING or the current
280 client encoding, even if the data does not pass through the client but
281 is read from or written to a file directly by the server.
282 COPY stops operation at the first error. This should not lead to
284 problems in the event of a COPY TO, but the target table will already
285 have received earlier rows in a COPY FROM. These rows will not be
286 visible or accessible, but they still occupy disk space. This might
287 amount to a considerable amount of wasted disk space if the failure
288 happened well into a large copy operation. You might wish to invoke
289 VACUUM to recover the wasted space.
290 FORCE_NULL and FORCE_NOT_NULL can be used simultaneously on the same
292 column. This results in converting quoted null strings to null values
293 and unquoted null strings to empty strings.
294
296 Text Format
297 When the text format is used, the data read or written is a text file
298 with one line per table row. Columns in a row are separated by the
299 delimiter character. The column values themselves are strings generated
300 by the output function, or acceptable to the input function, of each
301 attribute's data type. The specified null string is used in place of
302 columns that are null. COPY FROM will raise an error if any line of
303 the input file contains more or fewer columns than are expected.
304 End of data can be represented by a single line containing just
306 backslash-period (\.). An end-of-data marker is not necessary when
307 reading from a file, since the end of file serves perfectly well; it is
308 needed only when copying data to or from client applications using
309 pre-3.0 client protocol.
310 Backslash characters (\) can be used in the COPY data to quote data
312 characters that might otherwise be taken as row or column delimiters.
313 In particular, the following characters must be preceded by a backslash
314 if they appear as part of a column value: backslash itself, newline,
315 carriage return, and the current delimiter character.
316 The specified null string is sent by COPY TO without adding any
318 backslashes; conversely, COPY FROM matches the input against the null
319 string before removing backslashes. Therefore, a null string such as \N
320 cannot be confused with the actual data value \N (which would be
321 represented as \\N).
322 The following special backslash sequences are recognized by COPY FROM:
324 ┌─────────┬────────────────────────────┐
326 │Sequence │ Represents │
327 ├─────────┼────────────────────────────┤
328 │\b │ Backspace (ASCII 8) │
329 ├─────────┼────────────────────────────┤
330 │\f │ Form feed (ASCII 12) │
331 ├─────────┼────────────────────────────┤
332 │\n │ Newline (ASCII 10) │
333 ├─────────┼────────────────────────────┤
334 │\r │ Carriage return (ASCII 13) │
335 ├─────────┼────────────────────────────┤
336 │\t │ Tab (ASCII 9) │
337 ├─────────┼────────────────────────────┤
338 │\v │ Vertical tab (ASCII 11) │
339 ├─────────┼────────────────────────────┤
340 │\digits │ Backslash followed by one │
341 │ │ to three octal digits │
342 │ │ specifies │
343 │ │ the byte with that │
344 │ │ numeric code │
345 ├─────────┼────────────────────────────┤
346 │\xdigits │ Backslash x followed by │
347 │ │ one or two hex digits │
348 │ │ specifies │
349 │ │ the byte with that │
350 │ │ numeric code │
351 └─────────┴────────────────────────────┘
352 Presently, COPY TO will never emit an octal or hex-digits backslash
353 sequence, but it does use the other sequences listed above for those
354 control characters.
355 Any other backslashed character that is not mentioned in the above
357 table will be taken to represent itself. However, beware of adding
358 backslashes unnecessarily, since that might accidentally produce a
359 string matching the end-of-data marker (\.) or the null string (\N by
360 default). These strings will be recognized before any other backslash
361 processing is done.
362 It is strongly recommended that applications generating COPY data
364 convert data newlines and carriage returns to the \n and \r sequences
365 respectively. At present it is possible to represent a data carriage
366 return by a backslash and carriage return, and to represent a data
367 newline by a backslash and newline. However, these representations
368 might not be accepted in future releases. They are also highly
369 vulnerable to corruption if the COPY file is transferred across
370 different machines (for example, from Unix to Windows or vice versa).
371 All backslash sequences are interpreted after encoding conversion. The
373 bytes specified with the octal and hex-digit backslash sequences must
374 form valid characters in the database encoding.
375 COPY TO will terminate each row with a Unix-style newline (“\n”).
377 Servers running on Microsoft Windows instead output carriage
378 return/newline (“\r\n”), but only for COPY to a server file; for
379 consistency across platforms, COPY TO STDOUT always sends “\n”
380 regardless of server platform. COPY FROM can handle lines ending with
381 newlines, carriage returns, or carriage return/newlines. To reduce the
382 risk of error due to un-backslashed newlines or carriage returns that
383 were meant as data, COPY FROM will complain if the line endings in the
384 input are not all alike.
385 CSV Format
387 This format option is used for importing and exporting the Comma
388 Separated Value (CSV) file format used by many other programs, such as
389 spreadsheets. Instead of the escaping rules used by PostgreSQL's
390 standard text format, it produces and recognizes the common CSV
391 escaping mechanism.
392 The values in each record are separated by the DELIMITER character. If
394 the value contains the delimiter character, the QUOTE character, the
395 NULL string, a carriage return, or line feed character, then the whole
396 value is prefixed and suffixed by the QUOTE character, and any
397 occurrence within the value of a QUOTE character or the ESCAPE
398 character is preceded by the escape character. You can also use
399 FORCE_QUOTE to force quotes when outputting non-NULL values in specific
400 columns.
401 The CSV format has no standard way to distinguish a NULL value from an
403 empty string. PostgreSQL's COPY handles this by quoting. A NULL is
404 output as the NULL parameter string and is not quoted, while a non-NULL
405 value matching the NULL parameter string is quoted. For example, with
406 the default settings, a NULL is written as an unquoted empty string,
407 while an empty string data value is written with double quotes ("").
408 Reading values follows similar rules. You can use FORCE_NOT_NULL to
409 prevent NULL input comparisons for specific columns. You can also use
410 FORCE_NULL to convert quoted null string data values to NULL.
411 Because backslash is not a special character in the CSV format, \., the
413 end-of-data marker, could also appear as a data value. To avoid any
414 misinterpretation, a \. data value appearing as a lone entry on a line
415 is automatically quoted on output, and on input, if quoted, is not
416 interpreted as the end-of-data marker. If you are loading a file
417 created by another application that has a single unquoted column and
418 might have a value of \., you might need to quote that value in the
419 input file.
420 Note
422 In CSV format, all characters are significant. A quoted value
423 surrounded by white space, or any characters other than DELIMITER,
424 will include those characters. This can cause errors if you import
425 data from a system that pads CSV lines with white space out to some
426 fixed width. If such a situation arises you might need to
427 preprocess the CSV file to remove the trailing white space, before
428 importing the data into PostgreSQL.
429 Note
431 CSV format will both recognize and produce CSV files with quoted
432 values containing embedded carriage returns and line feeds. Thus
433 the files are not strictly one line per table row like text-format
434 files.
435 Note
437 Many programs produce strange and occasionally perverse CSV files,
438 so the file format is more a convention than a standard. Thus you
439 might encounter some files that cannot be imported using this
440 mechanism, and COPY might produce files that other programs cannot
441 process.
442 Binary Format
444 The binary format option causes all data to be stored/read as binary
445 format rather than as text. It is somewhat faster than the text and CSV
446 formats, but a binary-format file is less portable across machine
447 architectures and PostgreSQL versions. Also, the binary format is very
448 data type specific; for example it will not work to output binary data
449 from a smallint column and read it into an integer column, even though
450 that would work fine in text format.
451 The binary file format consists of a file header, zero or more tuples
453 containing the row data, and a file trailer. Headers and data are in
454 network byte order.
455 Note
457 PostgreSQL releases before 7.4 used a different binary file format.
458 File Header
460 The file header consists of 15 bytes of fixed fields, followed by a
461 variable-length header extension area. The fixed fields are:
462 Signature
464 11-byte sequence PGCOPY\n\377\r\n\0 — note that the zero byte
465 is a required part of the signature. (The signature is designed
466 to allow easy identification of files that have been munged by
467 a non-8-bit-clean transfer. This signature will be changed by
468 end-of-line-translation filters, dropped zero bytes, dropped
469 high bits, or parity changes.)
470 Flags field
472 32-bit integer bit mask to denote important aspects of the file
473 format. Bits are numbered from 0 (LSB) to 31 (MSB). Note that
474 this field is stored in network byte order (most significant
475 byte first), as are all the integer fields used in the file
476 format. Bits 16–31 are reserved to denote critical file format
477 issues; a reader should abort if it finds an unexpected bit set
478 in this range. Bits 0–15 are reserved to signal
479 backwards-compatible format issues; a reader should simply
480 ignore any unexpected bits set in this range. Currently only
481 one flag bit is defined, and the rest must be zero:
482 Bit 16
484 If 1, OIDs are included in the data; if 0, not. Oid system
485 columns are not supported in PostgreSQL anymore, but the
486 format still contains the indicator.
487 Header extension area length
489 32-bit integer, length in bytes of remainder of header, not
490 including self. Currently, this is zero, and the first tuple
491 follows immediately. Future changes to the format might allow
492 additional data to be present in the header. A reader should
493 silently skip over any header extension data it does not know
494 what to do with.
495 The header extension area is envisioned to contain a sequence of
497 self-identifying chunks. The flags field is not intended to tell
498 readers what is in the extension area. Specific design of header
499 extension contents is left for a later release.
500 This design allows for both backwards-compatible header additions
502 (add header extension chunks, or set low-order flag bits) and
503 non-backwards-compatible changes (set high-order flag bits to
504 signal such changes, and add supporting data to the extension area
505 if needed).
506 Tuples
508 Each tuple begins with a 16-bit integer count of the number of
509 fields in the tuple. (Presently, all tuples in a table will have
510 the same count, but that might not always be true.) Then, repeated
511 for each field in the tuple, there is a 32-bit length word followed
512 by that many bytes of field data. (The length word does not include
513 itself, and can be zero.) As a special case, -1 indicates a NULL
514 field value. No value bytes follow in the NULL case.
515 There is no alignment padding or any other extra data between
517 fields.
518 Presently, all data values in a binary-format file are assumed to
520 be in binary format (format code one). It is anticipated that a
521 future extension might add a header field that allows per-column
522 format codes to be specified.
523 To determine the appropriate binary format for the actual tuple
525 data you should consult the PostgreSQL source, in particular the
526 *send and *recv functions for each column's data type (typically
527 these functions are found in the src/backend/utils/adt/ directory
528 of the source distribution).
529 If OIDs are included in the file, the OID field immediately follows
531 the field-count word. It is a normal field except that it's not
532 included in the field-count. Note that oid system columns are not
533 supported in current versions of PostgreSQL.
534 File Trailer
536 The file trailer consists of a 16-bit integer word containing -1.
537 This is easily distinguished from a tuple's field-count word.
538 A reader should report an error if a field-count word is neither -1
540 nor the expected number of columns. This provides an extra check
541 against somehow getting out of sync with the data.
542
544 The following example copies a table to the client using the vertical
545 bar (|) as the field delimiter:
546 COPY country TO STDOUT (DELIMITER '|');
548 To copy data from a file into the country table:
550 COPY country FROM '/usr1/proj/bray/sql/country_data';
552 To copy into a file just the countries whose names start with 'A':
554 COPY (SELECT * FROM country WHERE country_name LIKE 'A%') TO '/usr1/proj/bray/sql/a_list_countries.copy';
556 To copy into a compressed file, you can pipe the output through an
558 external compression program:
559 COPY country TO PROGRAM 'gzip > /usr1/proj/bray/sql/country_data.gz';
561 Here is a sample of data suitable for copying into a table from STDIN:
563 AF AFGHANISTAN
565 AL ALBANIA
566 DZ ALGERIA
567 ZM ZAMBIA
568 ZW ZIMBABWE
569 Note that the white space on each line is actually a tab character.
571 The following is the same data, output in binary format. The data is
573 shown after filtering through the Unix utility od -c. The table has
574 three columns; the first has type char(2), the second has type text,
575 and the third has type integer. All the rows have a null value in the
576 third column.
577 0000000 P G C O P Y \n 377 \r \n \0 \0 \0 \0 \0 \0
579 0000020 \0 \0 \0 \0 003 \0 \0 \0 002 A F \0 \0 \0 013 A
580 0000040 F G H A N I S T A N 377 377 377 377 \0 003
581 0000060 \0 \0 \0 002 A L \0 \0 \0 007 A L B A N I
582 0000100 A 377 377 377 377 \0 003 \0 \0 \0 002 D Z \0 \0 \0
583 0000120 007 A L G E R I A 377 377 377 377 \0 003 \0 \0
584 0000140 \0 002 Z M \0 \0 \0 006 Z A M B I A 377 377
585 0000160 377 377 \0 003 \0 \0 \0 002 Z W \0 \0 \0 \b Z I
586 0000200 M B A B W E 377 377 377 377 377 377
587
589 There is no COPY statement in the SQL standard.
590 The following syntax was used before PostgreSQL version 9.0 and is
592 still supported:
593 COPY table_name [ ( column_name [, ...] ) ]
595 FROM { 'filename' | STDIN }
596 [ [ WITH ]
597 [ BINARY ]
598 [ DELIMITER [ AS ] 'delimiter_character' ]
599 [ NULL [ AS ] 'null_string' ]
600 [ CSV [ HEADER ]
601 [ QUOTE [ AS ] 'quote_character' ]
602 [ ESCAPE [ AS ] 'escape_character' ]
603 [ FORCE NOT NULL column_name [, ...] ] ] ]
604 COPY { table_name [ ( column_name [, ...] ) ] | ( query ) }
606 TO { 'filename' | STDOUT }
607 [ [ WITH ]
608 [ BINARY ]
609 [ DELIMITER [ AS ] 'delimiter_character' ]
610 [ NULL [ AS ] 'null_string' ]
611 [ CSV [ HEADER ]
612 [ QUOTE [ AS ] 'quote_character' ]
613 [ ESCAPE [ AS ] 'escape_character' ]
614 [ FORCE QUOTE { column_name [, ...] | * } ] ] ]
615 Note that in this syntax, BINARY and CSV are treated as independent
617 keywords, not as arguments of a FORMAT option.
618 The following syntax was used before PostgreSQL version 7.3 and is
620 still supported:
621 COPY [ BINARY ] table_name
623 FROM { 'filename' | STDIN }
624 [ [USING] DELIMITERS 'delimiter_character' ]
625 [ WITH NULL AS 'null_string' ]
626 COPY [ BINARY ] table_name
628 TO { 'filename' | STDOUT }
629 [ [USING] DELIMITERS 'delimiter_character' ]
630 [ WITH NULL AS 'null_string' ]
631
633 Section 28.4.6
634PostgreSQL 14.3 2022 COPY(7)