What Happens when using Direct Option in Copy , Insert, Update Command
Moderator: NorbertKrupa
What Happens when using Direct Option in Copy , Insert, Update Command
In Document it says Direct options allows data to be moved directly to WOS [ Secondary storage]. But How does it happen during processing. Sorry if I am wrong, According to the computer knowledge I have gained, the data cannot directly move to harddisk without passing main memory. If that is the case then what really happens when using Direct options. Please help me understand
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: What Happens when using Direct Option in Copy , Insert, Update Command
Hi,
There is a resource pool named WOSDATA that is set up in main memory specifically to hold projection data prior to being written to disk. The default size is 2 GB.
I'd imagine that data would have to pass through the host's main memory modules via the Vertica process in some manner, but it won't be placed the the special WOS area.
There is a resource pool named WOSDATA that is set up in main memory specifically to hold projection data prior to being written to disk. The default size is 2 GB.
Code: Select all
dbadmin=> select name, memorysize, maxmemorysize from resource_pools where name = 'wosdata';
name | memorysize | maxmemorysize
---------+------------+---------------
wosdata | 2G | 2G
(1 row)
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.