Update direct_path_load.mdx

[yuki-tei]

Hi,
Greetings. Hope you are doing well and healthy.

What Changed?

This same issue is found initially in EPAS15 but still exists in EPAS18.
Since its impact is huge, note shall be described in this page. Also, this change should be reflected into all affected versions:
15~18

[enterprisedb@edbsup04 ~]$ psql -p 5446
psql (18.3.0)
Type "help" for help.

edb=# SELECT version()
edb-# ;
                                                                     version
-------------------------------------------------------------------------------------------------------------------------------------------------
 PostgreSQL 18.3 (EnterpriseDB Advanced Server 18.3.0) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit
(1 row)

edb=# CREATE TABLE test(col1 int);
CREATE TABLE
edb=#
\q
[enterprisedb@edbsup04 ~]$ for i in $(seq 1 10)
do
  echo $i
done >> test.txt
[enterprisedb@edbsup04 ~]$ cat test.txt
1
2
3
4
5
6
7
8
9
10

[enterprisedb@edbsup04 ~]$ cat test.ctl
LOAD DATA
  INFILE 'test.txt'
  BADFILE 'test.bad'
APPEND
INTO TABLE test
  FIELDS TERMINATED BY ','
    OPTIONALLY ENCLOSED BY '"'
  TRAILING NULLCOLS
(
  col1
)
[enterprisedb@edbsup04 ~]$ edbldr -p 5446 USERID=enterprisedb/edb CONTROL=test.ctl DIRECT=TRUE
EDB*Loader: Copyright (c) 2007-2025, EnterpriseDB Corporation.

WARNING:  bulk load will not be WAL-logged
HINT:  Continuous archive will not include the loaded data. You must take a new base backup after the load is finished
Successfully processed (10) records
[enterprisedb@edbsup04 ~]$ psql
psql (18.3.0)
Type "help" for help.

edb=#
\q
[enterprisedb@edbsup04 ~]$ psql -p 5446
psql (18.3.0)
Type "help" for help.

edb=# SELECT * FROM test;
ERROR:  invalid page in block 0 of relation "base/14362/16384"

Hope you can take a look.

Kind Regards,
Yuki Tei

[tusharahuja]

The changes look good. We actually have an active Jira ticket for this (DB-2179), which is currently 'Ready for Committer.' Once that’s committed, users will receive a proper error message: '+edbldr error: ERROR: direct load is not possible with data encryption is enabled.'
If we add this warning to the documentation now, we’ll have to remove it shortly after the ticket is merged. We can either proceed with the doc update now or wait for DB-2179 to land (though I don’t have an ETA). I suggest we update the docs for now and revise them again once the ticket is committed.

[nidhibhammar]

Approved.

@anjali-edb, Create a DOCS JIRA to revert the doc changes when DB-2179 is committed and merged as suggested by Tushar.

[anjali-edb]

Thanks for the approval!

Merging this now to ensure users have the current manual warning. I have created JIRA 3596 to track the removal of this note once DB-2179 is committed and the native error message is live.